Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64bf23e0c1272898c3bdf1f82c17014ab23170341b98ca1f6e03bfd14dbf81f5

Tx prefix hash: c65170a2a7c4750223e6ad85c2613d7500320f2b776e32f7c51037846f2cf13e
Tx public key: 0dd2675bbe840d645b00601f8b7ecc85587b80bf74fb37066651120ad4ac2e4b
Timestamp: 1581630457 Timestamp [UCT]: 2020-02-13 21:47:37 Age [y:d:h:m:s]: 05:022:17:29:26
Block: 64267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169209 RingCT/type: yes/0
Extra: 010dd2675bbe840d645b00601f8b7ecc85587b80bf74fb37066651120ad4ac2e4b02110000004956c366d3000000000000000000

1 output(s) for total of 375.887222107000 dcy

stealth address amount amount idx
00: b6a81689db503d31eda3a2a09f043968ec32455a6daad810b01b5f42e237e0ae 375.887222107000 118540 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": 64277, "vin": [ { "gen": { "height": 64267 } } ], "vout": [ { "amount": 375887222107, "target": { "key": "b6a81689db503d31eda3a2a09f043968ec32455a6daad810b01b5f42e237e0ae" } } ], "extra": [ 1, 13, 210, 103, 91, 190, 132, 13, 100, 91, 0, 96, 31, 139, 126, 204, 133, 88, 123, 128, 191, 116, 251, 55, 6, 102, 81, 18, 10, 212, 172, 46, 75, 2, 17, 0, 0, 0, 73, 86, 195, 102, 211, 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