Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eefcf5e3334223d7f6f4e1cb1afe9c3df3ce3bfa7b16fc1fed71f6b68bcb5e52

Tx prefix hash: 42d6a856078e1298fab49995ce97cd7313c7cc39c9972300739f98f6971ce7d6
Tx public key: a4f597ce0a85cb39be34e95ad0da81a3f2ab3f24d3da1826465ac612cc24eaad
Timestamp: 1763116098 Timestamp [UCT]: 2025-11-14 10:28:18 Age [y:d:h:m:s]: 00:048:16:37:10
Block: 1411885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34867 RingCT/type: yes/0
Extra: 01a4f597ce0a85cb39be34e95ad0da81a3f2ab3f24d3da1826465ac612cc24eaad0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 785fe34cb1400c0aee9d22ef936b3542b196b53c67d1d3fd6f9f20066368794a 0.600000000000 1900350 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": 1411895, "vin": [ { "gen": { "height": 1411885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "785fe34cb1400c0aee9d22ef936b3542b196b53c67d1d3fd6f9f20066368794a" } } ], "extra": [ 1, 164, 245, 151, 206, 10, 133, 203, 57, 190, 52, 233, 90, 208, 218, 129, 163, 242, 171, 63, 36, 211, 218, 24, 38, 70, 90, 198, 18, 204, 36, 234, 173, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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