Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 181dceaae7dd28be882c35eb8548755c50d8c3527f69985463f5d145ddcb7abd

Tx prefix hash: 5004e8305fc94a6cdd660fb3a365c26d352f8d114a37723f0fdb60fdb3e362cb
Tx public key: 2dfd4330e94c7fcc72d492e188cebf321ff581e674ff7e59a8bbcef10cfb517d
Timestamp: 1708867028 Timestamp [UCT]: 2024-02-25 13:17:08 Age [y:d:h:m:s]: 01:269:00:33:30
Block: 965264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451008 RingCT/type: yes/0
Extra: 012dfd4330e94c7fcc72d492e188cebf321ff581e674ff7e59a8bbcef10cfb517d02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f53d4ea7609cef65b9619daa4403e296a0419e927f65b3da8ead6517bf11afd 0.600000000000 1425013 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": 965274, "vin": [ { "gen": { "height": 965264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f53d4ea7609cef65b9619daa4403e296a0419e927f65b3da8ead6517bf11afd" } } ], "extra": [ 1, 45, 253, 67, 48, 233, 76, 127, 204, 114, 212, 146, 225, 136, 206, 191, 50, 31, 245, 129, 230, 116, 255, 126, 89, 168, 187, 206, 241, 12, 251, 81, 125, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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