Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c19ee0558fb781d9f99cea5dcf7d981fb879e371e0dca4d408f14fb6951e975

Tx prefix hash: 387b4ef5c3127593b4061c69b45ba74cdc012b40b2d1085b40e5600699493ab2
Tx public key: e10bed790117aedf4f3d6ef6cd3abe0f1b2af8d024edaa275caaf4da2a4183a1
Timestamp: 1730320040 Timestamp [UCT]: 2024-10-30 20:27:20 Age [y:d:h:m:s]: 00:143:02:35:18
Block: 1143041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102110 RingCT/type: yes/0
Extra: 01e10bed790117aedf4f3d6ef6cd3abe0f1b2af8d024edaa275caaf4da2a4183a10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ecfb97644607c0a42dfc6f754f59ae36e8f6f641194c7dacc62a692301a0338 0.600000000000 1626898 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": 1143051, "vin": [ { "gen": { "height": 1143041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ecfb97644607c0a42dfc6f754f59ae36e8f6f641194c7dacc62a692301a0338" } } ], "extra": [ 1, 225, 11, 237, 121, 1, 23, 174, 223, 79, 61, 110, 246, 205, 58, 190, 15, 27, 42, 248, 208, 36, 237, 170, 39, 92, 170, 244, 218, 42, 65, 131, 161, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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