Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e7320c9556b47d0483f179ca26556662e5c60bff5a4bf3ca5bce5b940137ca

Tx prefix hash: b82d107166acef23ab040eba88c49c29188d0d44329e56cf48ab58ead1adfd24
Tx public key: d1b3e2ec6d7fbd815f513439accdf238b19c6d5ec9c0c74a182f34330a5fb314
Timestamp: 1754881465 Timestamp [UCT]: 2025-08-11 03:04:25 Age [y:d:h:m:s]: 00:006:15:51:30
Block: 1344544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4138 RingCT/type: yes/0
Extra: 01d1b3e2ec6d7fbd815f513439accdf238b19c6d5ec9c0c74a182f34330a5fb31402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1caf3a193fa8873f043942141d3935499b8721377052e468b6efdfa37c26ba0c 0.600000000000 1832429 of 15

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": 1344554, "vin": [ { "gen": { "height": 1344544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1caf3a193fa8873f043942141d3935499b8721377052e468b6efdfa37c26ba0c" } } ], "extra": [ 1, 209, 179, 226, 236, 109, 127, 189, 129, 95, 81, 52, 57, 172, 205, 242, 56, 177, 156, 109, 94, 201, 192, 199, 74, 24, 47, 52, 51, 10, 95, 179, 20, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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