Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ab9bb4e529627732d65d4cea799cc8e8c3aa4f86c50e9d48f9abcc65cdc528b

Tx prefix hash: 8a9730ba54528615d44b26a8d954b33fcdc9ad2f85957e3a9b0e9a234ea8f799
Tx public key: 3c771bca54220f7afaf2104f7ff386145b935774feff1f74f5080efb519b57a6
Timestamp: 1725882959 Timestamp [UCT]: 2024-09-09 11:55:59 Age [y:d:h:m:s]: 00:121:16:32:44
Block: 1106335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87019 RingCT/type: yes/0
Extra: 013c771bca54220f7afaf2104f7ff386145b935774feff1f74f5080efb519b57a602110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab53cc4944dca715ce9ae6227ef53d7d34838e7dd702cc553fe59654f823a5dd 0.600000000000 1583934 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": 1106345, "vin": [ { "gen": { "height": 1106335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab53cc4944dca715ce9ae6227ef53d7d34838e7dd702cc553fe59654f823a5dd" } } ], "extra": [ 1, 60, 119, 27, 202, 84, 34, 15, 122, 250, 242, 16, 79, 127, 243, 134, 20, 91, 147, 87, 116, 254, 255, 31, 116, 245, 8, 14, 251, 81, 155, 87, 166, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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