Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a495754a5d978b15ec8a440f3d792f67c36570554ae3449cc92a6fbf43a10c4

Tx prefix hash: ad845f6bbf937b46aea14d2741518ecfa7a5a5db2d8b86e10d218c24268ed9b0
Tx public key: dcfb87724333436dfe972d2caaeff543d06905fef6e2c083eef78c2895376b3d
Timestamp: 1721809386 Timestamp [UCT]: 2024-07-24 08:23:06 Age [y:d:h:m:s]: 01:105:17:09:35
Block: 1072553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334044 RingCT/type: yes/0
Extra: 01dcfb87724333436dfe972d2caaeff543d06905fef6e2c083eef78c2895376b3d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeb41ff96d1b79e46ecd76e373b4139740244d1d4ab79f328105e9150b57c977 0.600000000000 1545028 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": 1072563, "vin": [ { "gen": { "height": 1072553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeb41ff96d1b79e46ecd76e373b4139740244d1d4ab79f328105e9150b57c977" } } ], "extra": [ 1, 220, 251, 135, 114, 67, 51, 67, 109, 254, 151, 45, 44, 170, 239, 245, 67, 208, 105, 5, 254, 246, 226, 192, 131, 238, 247, 140, 40, 149, 55, 107, 61, 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