Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4b0943e514211f572bc4c6a59282cb90295b26e3cc13f09b99d9bb04d318022

Tx prefix hash: 5b0f629a9afef1d1bb740bd3703fd47b2f581797f65e18a9f608450a55ee0452
Tx public key: 834ca00d466f98509101b2039e88e875eee2f84ae17ad951a21cc45953a203cd
Timestamp: 1581799629 Timestamp [UCT]: 2020-02-15 20:47:09 Age [y:d:h:m:s]: 04:264:14:03:09
Block: 65569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081469 RingCT/type: yes/0
Extra: 01834ca00d466f98509101b2039e88e875eee2f84ae17ad951a21cc45953a203cd02110000000dd81c26c0000000000000000000

1 output(s) for total of 372.171826797000 dcy

stealth address amount amount idx
00: 602c5063b5d4ec85fdf3ebc409ab308a939f3dda45727be1ee9f87cb5e9973c9 372.171826797000 120996 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": 65579, "vin": [ { "gen": { "height": 65569 } } ], "vout": [ { "amount": 372171826797, "target": { "key": "602c5063b5d4ec85fdf3ebc409ab308a939f3dda45727be1ee9f87cb5e9973c9" } } ], "extra": [ 1, 131, 76, 160, 13, 70, 111, 152, 80, 145, 1, 178, 3, 158, 136, 232, 117, 238, 226, 248, 74, 225, 122, 217, 81, 162, 28, 196, 89, 83, 162, 3, 205, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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