Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f2af0d456212176e1c07658a16b1c036185174e4eafc31a1a083d48b2a4df2d

Tx prefix hash: b45bedd1eeb40d71d403fe2d1f2169af1de9c3722aa7bd5af43235f5f6025111
Tx public key: a43f08f17b3cc0817c6a970350dd3c2fee0e0459335854fa549e89ba201eecf5
Timestamp: 1705017507 Timestamp [UCT]: 2024-01-11 23:58:27 Age [y:d:h:m:s]: 01:131:11:08:13
Block: 933326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355103 RingCT/type: yes/0
Extra: 01a43f08f17b3cc0817c6a970350dd3c2fee0e0459335854fa549e89ba201eecf50211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63dc032d923b46716e6700a8843aa585dbd56fa495dd9da186ba8bc8e58c37e1 0.600000000000 1391288 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": 933336, "vin": [ { "gen": { "height": 933326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63dc032d923b46716e6700a8843aa585dbd56fa495dd9da186ba8bc8e58c37e1" } } ], "extra": [ 1, 164, 63, 8, 241, 123, 60, 192, 129, 124, 106, 151, 3, 80, 221, 60, 47, 238, 14, 4, 89, 51, 88, 84, 250, 84, 158, 137, 186, 32, 30, 236, 245, 2, 17, 0, 0, 0, 9, 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