Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99fe6e8275ae1314d656b73bd2d5956523256bb0b7a6a8d303d8c5ac2e53d3c1

Tx prefix hash: 25850058b7d830788d9ac8e88ce1e3779ae4b98bb78444e90e49803bf29f9882
Tx public key: ef4adee9df188cda388c48f2758b10aa951f69900248d49edab3cf3d6470e2fb
Timestamp: 1743825722 Timestamp [UCT]: 2025-04-05 04:02:02 Age [y:d:h:m:s]: 00:275:18:44:13
Block: 1254583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194924 RingCT/type: yes/0
Extra: 01ef4adee9df188cda388c48f2758b10aa951f69900248d49edab3cf3d6470e2fb0211000000044060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6d45007939c63305c0bd0f0cad7e5fcc3ff84e608ac17cc2a41d48a7bea34bb 0.600000000000 1741664 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": 1254593, "vin": [ { "gen": { "height": 1254583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6d45007939c63305c0bd0f0cad7e5fcc3ff84e608ac17cc2a41d48a7bea34bb" } } ], "extra": [ 1, 239, 74, 222, 233, 223, 24, 140, 218, 56, 140, 72, 242, 117, 139, 16, 170, 149, 31, 105, 144, 2, 72, 212, 158, 218, 179, 207, 61, 100, 112, 226, 251, 2, 17, 0, 0, 0, 4, 64, 96, 246, 210, 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