Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a6cca84c9ab594be69c96e66d4a1a0b6c13747406f9fe5895f62013731281f4

Tx prefix hash: 7b678c2ba787a826fc3b91501f94510c5fc456037bea83cff3e986de71bb3fbb
Tx public key: 436affab454656beab4e9be148cc0d1a1bf2918d99396cebfc3512ac9e4276ca
Timestamp: 1582976813 Timestamp [UCT]: 2020-02-29 11:46:53 Age [y:d:h:m:s]: 04:342:00:47:59
Block: 74034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137890 RingCT/type: yes/0
Extra: 01436affab454656beab4e9be148cc0d1a1bf2918d99396cebfc3512ac9e4276ca02110000008e026b59f3000000000000000000

1 output(s) for total of 348.895544740000 dcy

stealth address amount amount idx
00: a992022dcd7084e4b6ea060d0c974e8a3b94de511b650fe2f3020fdf4677bb3c 348.895544740000 136828 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": 74044, "vin": [ { "gen": { "height": 74034 } } ], "vout": [ { "amount": 348895544740, "target": { "key": "a992022dcd7084e4b6ea060d0c974e8a3b94de511b650fe2f3020fdf4677bb3c" } } ], "extra": [ 1, 67, 106, 255, 171, 69, 70, 86, 190, 171, 78, 155, 225, 72, 204, 13, 26, 27, 242, 145, 141, 153, 57, 108, 235, 252, 53, 18, 172, 158, 66, 118, 202, 2, 17, 0, 0, 0, 142, 2, 107, 89, 243, 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