Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b79ece517744ff2874cd6672612f773efbe2045a484f2a5701ff1343a762a697

Tx prefix hash: 494fcf3e8a7e946774b9a626a32cba4dcfc013c67e2cac9640dc285e2898a06f
Tx public key: dd8e253cc5d8bfca00cf8689dd2b01198a416c0419e25ccb133381b9d3574168
Timestamp: 1581687606 Timestamp [UCT]: 2020-02-14 13:40:06 Age [y:d:h:m:s]: 04:280:13:21:08
Block: 64874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092660 RingCT/type: yes/0
Extra: 01dd8e253cc5d8bfca00cf8689dd2b01198a416c0419e25ccb133381b9d3574168021100000002990c7e00000000000000000000

1 output(s) for total of 374.150490332000 dcy

stealth address amount amount idx
00: 216d8ee3c4f01328c8d0d6ab2d221cbd58ff2a834645ed532a7a56da7830c833 374.150490332000 119718 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": 64884, "vin": [ { "gen": { "height": 64874 } } ], "vout": [ { "amount": 374150490332, "target": { "key": "216d8ee3c4f01328c8d0d6ab2d221cbd58ff2a834645ed532a7a56da7830c833" } } ], "extra": [ 1, 221, 142, 37, 60, 197, 216, 191, 202, 0, 207, 134, 137, 221, 43, 1, 25, 138, 65, 108, 4, 25, 226, 92, 203, 19, 51, 129, 185, 211, 87, 65, 104, 2, 17, 0, 0, 0, 2, 153, 12, 126, 0, 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