Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8001b1f7bd9618d8f3e28f067e94d22a349502a84384b7c441f2ed4b215664d

Tx prefix hash: d00d18e5baf5ff477acb1872e0ef54f92abc62a13c4e0753b2cf4314affa71cc
Tx public key: c2cc97bc0e9b6f10052f746e03a7e8e35284e911aac90334176f006cbfcef23b
Timestamp: 1632402717 Timestamp [UCT]: 2021-09-23 13:11:57 Age [y:d:h:m:s]: 03:217:03:43:24
Block: 339471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 931241 RingCT/type: yes/0
Extra: 01c2cc97bc0e9b6f10052f746e03a7e8e35284e911aac90334176f006cbfcef23b0211000000e6f60c5d7e000000000000000000

1 output(s) for total of 46.046819047000 dcy

stealth address amount amount idx
00: 325dc27f54a3dcb178a6c2db77ca0a0f75bd085d3d83ad6709836fd3569701b1 46.046819047000 698164 of 0

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": 339481, "vin": [ { "gen": { "height": 339471 } } ], "vout": [ { "amount": 46046819047, "target": { "key": "325dc27f54a3dcb178a6c2db77ca0a0f75bd085d3d83ad6709836fd3569701b1" } } ], "extra": [ 1, 194, 204, 151, 188, 14, 155, 111, 16, 5, 47, 116, 110, 3, 167, 232, 227, 82, 132, 233, 17, 170, 201, 3, 52, 23, 111, 0, 108, 191, 206, 242, 59, 2, 17, 0, 0, 0, 230, 246, 12, 93, 126, 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