Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5d33d31df859b9caa54461617bfb9a7bf6dc19519ba4588f521e28462296d3b

Tx prefix hash: 428e3f5ce100f099b2ae4d4fb26c91f0b53d6f4da0467cd404d6f6e5d76b2ac1
Tx public key: 19402cb91ee5944b969c4a120102aca156318f94e91379be81b479da718e3d76
Timestamp: 1580928705 Timestamp [UCT]: 2020-02-05 18:51:45 Age [y:d:h:m:s]: 04:297:09:42:13
Block: 59358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103956 RingCT/type: yes/0
Extra: 0119402cb91ee5944b969c4a120102aca156318f94e91379be81b479da718e3d7602110000000f8a2ee0d9000000000000000000

1 output(s) for total of 390.251840000000 dcy

stealth address amount amount idx
00: c8451214f2211b2738830773da8e7823b7eac40a5194046eefd061c94b8545dd 390.251840000000 109616 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": 59368, "vin": [ { "gen": { "height": 59358 } } ], "vout": [ { "amount": 390251840000, "target": { "key": "c8451214f2211b2738830773da8e7823b7eac40a5194046eefd061c94b8545dd" } } ], "extra": [ 1, 25, 64, 44, 185, 30, 229, 148, 75, 150, 156, 74, 18, 1, 2, 172, 161, 86, 49, 143, 148, 233, 19, 121, 190, 129, 180, 121, 218, 113, 142, 61, 118, 2, 17, 0, 0, 0, 15, 138, 46, 224, 217, 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