Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54257e324a72f209277c4294b985ece3d680a1dc7577ec5f2e3df879d9349af3

Tx prefix hash: 940f68d235ae90b4f244da3c09b40465394d13397286678b564c85f82b45e43b
Tx public key: e1895ac2eb48de1bb6697a49efb5cd7ae90a029a152cec2e87bb1640704e8884
Timestamp: 1698788122 Timestamp [UCT]: 2023-10-31 21:35:22 Age [y:d:h:m:s]: 02:008:10:22:18
Block: 881909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525606 RingCT/type: yes/0
Extra: 01e1895ac2eb48de1bb6697a49efb5cd7ae90a029a152cec2e87bb1640704e888402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.734293012000 dcy

stealth address amount amount idx
00: e9553a9fdc5ed79eca266c4b669126a8f71fdc0997d4dc93022cfaf047e98cc7 0.734293012000 1337535 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": 881919, "vin": [ { "gen": { "height": 881909 } } ], "vout": [ { "amount": 734293012, "target": { "key": "e9553a9fdc5ed79eca266c4b669126a8f71fdc0997d4dc93022cfaf047e98cc7" } } ], "extra": [ 1, 225, 137, 90, 194, 235, 72, 222, 27, 182, 105, 122, 73, 239, 181, 205, 122, 233, 10, 2, 154, 21, 44, 236, 46, 135, 187, 22, 64, 112, 78, 136, 132, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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