Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 519b0dc76b065814295a33179c896b9a0f216896a8e213ff29bda86497f6a38a

Tx prefix hash: 49ac1572e86fb9edd9a85926c14f912670e74e18f29e12c1fadcf2579dbf23c3
Tx public key: 21fdda4fcb3229e7a07cc2b55b81224010fdbefea821fc1dae58fb208e522ce1
Timestamp: 1721159172 Timestamp [UCT]: 2024-07-16 19:46:12 Age [y:d:h:m:s]: 00:194:23:56:56
Block: 1067178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139258 RingCT/type: yes/0
Extra: 0121fdda4fcb3229e7a07cc2b55b81224010fdbefea821fc1dae58fb208e522ce102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b030476a6141a1990b8f1ad16b2ac876d7e6f4a29860ea19bc0fd767285681b5 0.600000000000 1537921 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": 1067188, "vin": [ { "gen": { "height": 1067178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b030476a6141a1990b8f1ad16b2ac876d7e6f4a29860ea19bc0fd767285681b5" } } ], "extra": [ 1, 33, 253, 218, 79, 203, 50, 41, 231, 160, 124, 194, 181, 91, 129, 34, 64, 16, 253, 190, 254, 168, 33, 252, 29, 174, 88, 251, 32, 142, 82, 44, 225, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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