Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65961ec7bbdce440a31c7e76aad9a9d7add8ee792f9c14219c7d66e709458ebe

Tx prefix hash: cef5b714f6431e66ea14f27bc689661d88e812ce72cd7b02dc7864ea1a4d29ca
Tx public key: bce6774ea199c4e8fefb34e92bafb1ae89e9a2856e36c2c0ca8368db23acc4ce
Timestamp: 1582641205 Timestamp [UCT]: 2020-02-25 14:33:25 Age [y:d:h:m:s]: 05:253:15:55:01
Block: 72172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1332432 RingCT/type: yes/0
Extra: 01bce6774ea199c4e8fefb34e92bafb1ae89e9a2856e36c2c0ca8368db23acc4ce02110000000103d36d11000000000000000000

1 output(s) for total of 353.887322116000 dcy

stealth address amount amount idx
00: 57fb00023e21b6e6962f9976854f3c82053fc7262a8c86f38fdae9eeaab6f7c0 353.887322116000 133320 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": 72182, "vin": [ { "gen": { "height": 72172 } } ], "vout": [ { "amount": 353887322116, "target": { "key": "57fb00023e21b6e6962f9976854f3c82053fc7262a8c86f38fdae9eeaab6f7c0" } } ], "extra": [ 1, 188, 230, 119, 78, 161, 153, 196, 232, 254, 251, 52, 233, 43, 175, 177, 174, 137, 233, 162, 133, 110, 54, 194, 192, 202, 131, 104, 219, 35, 172, 196, 206, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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