Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39e09b570c1c565df7b22eb3ec9fc702437c8d3bcebfac59dae1a4999d5d79db

Tx prefix hash: 8b501dd4f85836752170fa3256e8de9ad396c62d1b727b78e8a08ca55f964f35
Tx public key: ef8ac3e23ce7044843ab6f54e5a755a528607a98c8fb9aeb691e58187909fc0d
Timestamp: 1764965054 Timestamp [UCT]: 2025-12-05 20:04:14 Age [y:d:h:m:s]: 00:016:16:00:18
Block: 1427199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11935 RingCT/type: yes/0
Extra: 01ef8ac3e23ce7044843ab6f54e5a755a528607a98c8fb9aeb691e58187909fc0d021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 182827a34fe54d1c38b1066a165339239bb75ac4c1c9fd4ab4c492055b6345fd 0.600000000000 1915898 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": 1427209, "vin": [ { "gen": { "height": 1427199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "182827a34fe54d1c38b1066a165339239bb75ac4c1c9fd4ab4c492055b6345fd" } } ], "extra": [ 1, 239, 138, 195, 226, 60, 231, 4, 72, 67, 171, 111, 84, 229, 167, 85, 165, 40, 96, 122, 152, 200, 251, 154, 235, 105, 30, 88, 24, 121, 9, 252, 13, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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