Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54df473d2bf2e82e31c00c6088e8c851e02ccf1e0dc9614e33b0c1bcd3aa16b3

Tx prefix hash: 217d71178a6589e2f54420a0a119eca95b8147b668eed58c3b49444bb1d8d38c
Tx public key: 519c9f2254d28157bb83fb7447db758bb2679e8f38011185f96dd61da4c0de27
Timestamp: 1733234813 Timestamp [UCT]: 2024-12-03 14:06:53 Age [y:d:h:m:s]: 00:036:12:21:31
Block: 1167176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26127 RingCT/type: yes/0
Extra: 01519c9f2254d28157bb83fb7447db758bb2679e8f38011185f96dd61da4c0de27021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 395b26d4aef1921f98b19f7a3aced5dcf5cb288c0f3545985e9f1ba4fff6184e 0.600000000000 1652871 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": 1167186, "vin": [ { "gen": { "height": 1167176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "395b26d4aef1921f98b19f7a3aced5dcf5cb288c0f3545985e9f1ba4fff6184e" } } ], "extra": [ 1, 81, 156, 159, 34, 84, 210, 129, 87, 187, 131, 251, 116, 71, 219, 117, 139, 178, 103, 158, 143, 56, 1, 17, 133, 249, 109, 214, 29, 164, 192, 222, 39, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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