Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcc62b4269de2592c6baaab7950e85c871fbf9a1b9c57248632b3c67da393e9c

Tx prefix hash: 9bdf590cff20018253f7921dca3a16af4efd5b75c372bc963fce1df8e1651e7e
Tx public key: f4aa08544ae2d6bbe63f9836bed85e0d3cb83d7688dbc804c4dc490e281a6d1f
Timestamp: 1576443682 Timestamp [UCT]: 2019-12-15 21:01:22 Age [y:d:h:m:s]: 04:326:16:41:13
Block: 27865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119254 RingCT/type: yes/0
Extra: 01f4aa08544ae2d6bbe63f9836bed85e0d3cb83d7688dbc804c4dc490e281a6d1f0211000000044ac5aa02000000000000000000

1 output(s) for total of 496.255034694000 dcy

stealth address amount amount idx
00: 9c415e622fb175e5c7b03fcd56f50e8ca143c3e38fcd9a9a5e038b6bc4a6df70 496.255034694000 46009 of 0

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": 27875, "vin": [ { "gen": { "height": 27865 } } ], "vout": [ { "amount": 496255034694, "target": { "key": "9c415e622fb175e5c7b03fcd56f50e8ca143c3e38fcd9a9a5e038b6bc4a6df70" } } ], "extra": [ 1, 244, 170, 8, 84, 74, 226, 214, 187, 230, 63, 152, 54, 190, 216, 94, 13, 60, 184, 61, 118, 136, 219, 200, 4, 196, 220, 73, 14, 40, 26, 109, 31, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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