Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f655ef3a4cc6c4c28557efab9636e1afa21d2401483b76e31cee40f3e9ecb4c

Tx prefix hash: eceb28156354f56b770f5837d05e4aec0162935b19fc27bd0a8213022ec51fbb
Tx public key: 078546c10f4f9baf14e009ce0c760dae34f9c14d3b0c89cbc085168c5e6c7e16
Timestamp: 1754524338 Timestamp [UCT]: 2025-08-06 23:52:18 Age [y:d:h:m:s]: 00:093:16:32:12
Block: 1341791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65976 RingCT/type: yes/0
Extra: 01078546c10f4f9baf14e009ce0c760dae34f9c14d3b0c89cbc085168c5e6c7e16021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e4bc4c70faaeb76be861e5f7704fd266a42492a0e760b01712d19db61242910 0.600000000000 1829618 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": 1341801, "vin": [ { "gen": { "height": 1341791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e4bc4c70faaeb76be861e5f7704fd266a42492a0e760b01712d19db61242910" } } ], "extra": [ 1, 7, 133, 70, 193, 15, 79, 155, 175, 20, 224, 9, 206, 12, 118, 13, 174, 52, 249, 193, 77, 59, 12, 137, 203, 192, 133, 22, 140, 94, 108, 126, 22, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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