Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a967c5a3c56688158a4dd1f1d517468d8418b546ad056e2f30dda2a17e334fb5

Tx prefix hash: 1658e8eca5d3257e1f65c3998b376e96dff6bd228a308beac37ec106cba68986
Tx public key: 722dcad19187531e193a4c3023bef38a77a50805a0ef3b8e1f92b6e1a94f4c72
Timestamp: 1727385089 Timestamp [UCT]: 2024-09-26 21:11:29 Age [y:d:h:m:s]: 00:106:22:29:53
Block: 1118777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76452 RingCT/type: yes/0
Extra: 01722dcad19187531e193a4c3023bef38a77a50805a0ef3b8e1f92b6e1a94f4c72021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edc6e8a06df2e0ab2343d3becd121ab7951688f79689c892346b76264f5d5d60 0.600000000000 1600090 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": 1118787, "vin": [ { "gen": { "height": 1118777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edc6e8a06df2e0ab2343d3becd121ab7951688f79689c892346b76264f5d5d60" } } ], "extra": [ 1, 114, 45, 202, 209, 145, 135, 83, 30, 25, 58, 76, 48, 35, 190, 243, 138, 119, 165, 8, 5, 160, 239, 59, 142, 31, 146, 182, 225, 169, 79, 76, 114, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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