Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc80d66aebc3ab3b236b3acd492a20c6eac4ba04132f217f9153e6ab884714e3

Tx prefix hash: 43a52a49608ffdca600d3d0bde35d56e941fe9bdd8d6669e1c2e2df7b9c3e1c6
Tx public key: be96164401f7a3f296f6925a139f9b0d936d78a0f548ccdf4f13908b578ba9d4
Timestamp: 1576643736 Timestamp [UCT]: 2019-12-18 04:35:36 Age [y:d:h:m:s]: 04:348:17:45:45
Block: 28373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136187 RingCT/type: yes/0
Extra: 01be96164401f7a3f296f6925a139f9b0d936d78a0f548ccdf4f13908b578ba9d40211000000479159db1e000000000000000000

1 output(s) for total of 494.298551132000 dcy

stealth address amount amount idx
00: 631d5cb66e1e6856f34d3737c006a5948a0be05270e9f55aecd2e5636908fced 494.298551132000 46917 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": 28383, "vin": [ { "gen": { "height": 28373 } } ], "vout": [ { "amount": 494298551132, "target": { "key": "631d5cb66e1e6856f34d3737c006a5948a0be05270e9f55aecd2e5636908fced" } } ], "extra": [ 1, 190, 150, 22, 68, 1, 247, 163, 242, 150, 246, 146, 90, 19, 159, 155, 13, 147, 109, 120, 160, 245, 72, 204, 223, 79, 19, 144, 139, 87, 139, 169, 212, 2, 17, 0, 0, 0, 71, 145, 89, 219, 30, 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