Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51e4a2d5a8dd33a33c25e0798580ee5021c94c621946b6197fe24a458496d1e3

Tx prefix hash: ef6c0cb44d8b380170d3154c660821ea0bb0e70cf28b84ee42a6c896bd1dfeda
Tx public key: d50e87d3bb96f2df2ab935e7260aef6cf280cae95597a7141a333e4fe5a797ff
Timestamp: 1731021495 Timestamp [UCT]: 2024-11-07 23:18:15 Age [y:d:h:m:s]: 00:224:16:23:00
Block: 1148842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160295 RingCT/type: yes/0
Extra: 01d50e87d3bb96f2df2ab935e7260aef6cf280cae95597a7141a333e4fe5a797ff021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45460e22fa1c9343ab00a09d4bf6491805288a935ff1a227b92871a95c65d358 0.600000000000 1633783 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": 1148852, "vin": [ { "gen": { "height": 1148842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45460e22fa1c9343ab00a09d4bf6491805288a935ff1a227b92871a95c65d358" } } ], "extra": [ 1, 213, 14, 135, 211, 187, 150, 242, 223, 42, 185, 53, 231, 38, 10, 239, 108, 242, 128, 202, 233, 85, 151, 167, 20, 26, 51, 62, 79, 229, 167, 151, 255, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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