Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ebbe18313ab146fbc1e7f1cfc0a314aa8cb14c22e831379688475219756ef4a

Tx prefix hash: 018d24b3c9f13585ae2887ce4d3a5b7af87cda6e37ddbccfa1042c8b11df6e76
Tx public key: 292b66e96e5e1c967bfab9fe3e99ea5418a3de90a8d2666fbd99adcd97774e43
Timestamp: 1581514879 Timestamp [UCT]: 2020-02-12 13:41:19 Age [y:d:h:m:s]: 05:032:01:47:57
Block: 63424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175787 RingCT/type: yes/0
Extra: 01292b66e96e5e1c967bfab9fe3e99ea5418a3de90a8d2666fbd99adcd97774e4302110000000103d36d11000000000000000000

1 output(s) for total of 378.312570997000 dcy

stealth address amount amount idx
00: 65a2cdc91205dd757fc47d3a5a21ffd60e9576a796696c7bca8aa5a834b978c0 378.312570997000 116974 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": 63434, "vin": [ { "gen": { "height": 63424 } } ], "vout": [ { "amount": 378312570997, "target": { "key": "65a2cdc91205dd757fc47d3a5a21ffd60e9576a796696c7bca8aa5a834b978c0" } } ], "extra": [ 1, 41, 43, 102, 233, 110, 94, 28, 150, 123, 250, 185, 254, 62, 153, 234, 84, 24, 163, 222, 144, 168, 210, 102, 111, 189, 153, 173, 205, 151, 119, 78, 67, 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