Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53ba300fe14ecd11325221e4360fb533126991a75333e429b324e8e91b0afa11

Tx prefix hash: 871917f8eda424b1ca8b582b133a6bf6c9efe7fe32b2ca76561110d544d2c085
Tx public key: 710a064a1a80e247ccf708f022a62d9415ec4a6b919edc082c4a6a42b9ca2076
Timestamp: 1736748692 Timestamp [UCT]: 2025-01-13 06:11:32 Age [y:d:h:m:s]: 00:065:21:36:07
Block: 1196266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46893 RingCT/type: yes/0
Extra: 01710a064a1a80e247ccf708f022a62d9415ec4a6b919edc082c4a6a42b9ca2076021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92bc064ae7941f339835c84210f9d280a0e241096a058855eaf85a41f32e54bc 0.600000000000 1682863 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": 1196276, "vin": [ { "gen": { "height": 1196266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92bc064ae7941f339835c84210f9d280a0e241096a058855eaf85a41f32e54bc" } } ], "extra": [ 1, 113, 10, 6, 74, 26, 128, 226, 71, 204, 247, 8, 240, 34, 166, 45, 148, 21, 236, 74, 107, 145, 158, 220, 8, 44, 74, 106, 66, 185, 202, 32, 118, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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