Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0e3519e63e97cb001d514932665f1566b6c7750da30919310979e2b41f2ae5c

Tx prefix hash: aed07dd5c532f2f7cca8dc33426f3cfadd6d91cc02e8ee497d62dbc2733117ff
Tx public key: 86032a0cfcafd3e127bff4bd0e575297ded344f1db4437225b49976e5923ff03
Timestamp: 1586616516 Timestamp [UCT]: 2020-04-11 14:48:36 Age [y:d:h:m:s]: 04:260:19:14:10
Block: 92996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091218 RingCT/type: yes/0
Extra: 0186032a0cfcafd3e127bff4bd0e575297ded344f1db4437225b49976e5923ff0302110000027e209b4bc8000000000000000000

1 output(s) for total of 301.902297764000 dcy

stealth address amount amount idx
00: 2f9afe1d48c29704e9ce3fc72883b3a32e95df8f372f69f501298a059334f354 301.902297764000 165676 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": 93006, "vin": [ { "gen": { "height": 92996 } } ], "vout": [ { "amount": 301902297764, "target": { "key": "2f9afe1d48c29704e9ce3fc72883b3a32e95df8f372f69f501298a059334f354" } } ], "extra": [ 1, 134, 3, 42, 12, 252, 175, 211, 225, 39, 191, 244, 189, 14, 87, 82, 151, 222, 211, 68, 241, 219, 68, 55, 34, 91, 73, 151, 110, 89, 35, 255, 3, 2, 17, 0, 0, 2, 126, 32, 155, 75, 200, 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