Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4c8cc8e5a7a99e211d7bb1c9370c0b65be21f0e8f52a364cd3df76d5849d5891

Tx prefix hash: c8da3335099c860cfd5f5aec851d60929c5396211b25e88260134faeb822ad5b
Tx public key: 53cddbfb01223a8669389a5523594e322bd8dadaf45fd68e12450db1e13393f3
Timestamp: 1728455096 Timestamp [UCT]: 2024-10-09 06:24:56 Age [y:d:h:m:s]: 00:106:14:38:01
Block: 1127647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76170 RingCT/type: yes/0
Extra: 0153cddbfb01223a8669389a5523594e322bd8dadaf45fd68e12450db1e13393f3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3aa2dfd782a2c3806a14f0a8dc45309b763140af6ec796b1c236c3919988197 0.600000000000 1610454 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1127657, "vin": [ { "gen": { "height": 1127647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3aa2dfd782a2c3806a14f0a8dc45309b763140af6ec796b1c236c3919988197" } } ], "extra": [ 1, 83, 205, 219, 251, 1, 34, 58, 134, 105, 56, 154, 85, 35, 89, 78, 50, 43, 216, 218, 218, 244, 95, 214, 142, 18, 69, 13, 177, 225, 51, 147, 243, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8