Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d2e14550011904125dcc08426a4871c25a5077466749e9a5369e1050c385511

Tx prefix hash: 5c783eb1615aff37cdb9df125d77715a2c3cc7cd8a9f72937162ef62d1d38b7b
Tx public key: 9c2bd1372bd4f6d7dec9d1dc251c49e46c57e5e8d5cbf161c22c0aca3ac198d8
Timestamp: 1592761029 Timestamp [UCT]: 2020-06-21 17:37:09 Age [y:d:h:m:s]: 04:194:13:03:58
Block: 110136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077554 RingCT/type: yes/0
Extra: 019c2bd1372bd4f6d7dec9d1dc251c49e46c57e5e8d5cbf161c22c0aca3ac198d802110000004846a11e8a000000000000000000

1 output(s) for total of 264.895426548000 dcy

stealth address amount amount idx
00: 0e0e6c27d5bf6aa2f365d19b745cc870f43da6e305a3a2da2c6c68d54e6f08cf 264.895426548000 190766 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": 110146, "vin": [ { "gen": { "height": 110136 } } ], "vout": [ { "amount": 264895426548, "target": { "key": "0e0e6c27d5bf6aa2f365d19b745cc870f43da6e305a3a2da2c6c68d54e6f08cf" } } ], "extra": [ 1, 156, 43, 209, 55, 43, 212, 246, 215, 222, 201, 209, 220, 37, 28, 73, 228, 108, 87, 229, 232, 213, 203, 241, 97, 194, 44, 10, 202, 58, 193, 152, 216, 2, 17, 0, 0, 0, 72, 70, 161, 30, 138, 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