Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67f755fc6a94276c0b14644dbbcdd6e3559299d322d7634cc4396bf4456a7394

Tx prefix hash: d6276313de624afc089494d19e1e83fbc10d249b9be7aed6244b4bd663b608d9
Tx public key: 86e0e87a17bf1ea271d1dc6a45410f7216bc5a4063bd2c1c4c179e5f275bebf8
Timestamp: 1575701303 Timestamp [UCT]: 2019-12-07 06:48:23 Age [y:d:h:m:s]: 05:062:19:55:33
Block: 22496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190572 RingCT/type: yes/0
Extra: 0186e0e87a17bf1ea271d1dc6a45410f7216bc5a4063bd2c1c4c179e5f275bebf802110000000b4943cd9f000000000000000000

1 output(s) for total of 516.966363706000 dcy

stealth address amount amount idx
00: 32c039f975b13699ce1d47444b28e711cd5d98e246105f4d5de3e5c3737294d1 516.966363706000 35529 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": 22506, "vin": [ { "gen": { "height": 22496 } } ], "vout": [ { "amount": 516966363706, "target": { "key": "32c039f975b13699ce1d47444b28e711cd5d98e246105f4d5de3e5c3737294d1" } } ], "extra": [ 1, 134, 224, 232, 122, 23, 191, 30, 162, 113, 209, 220, 106, 69, 65, 15, 114, 22, 188, 90, 64, 99, 189, 44, 28, 76, 23, 158, 95, 39, 91, 235, 248, 2, 17, 0, 0, 0, 11, 73, 67, 205, 159, 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