Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3a6e5d34aaeee9f16bc40de86d25cea59d53f9f7e276dc5a74402bc71562584

Tx prefix hash: f66fd48b51ef6cb2a0df1ddb09b51864cba322cb08b165afe081bd3cb78fcf4c
Tx public key: c9f920bb040584f86fec472abac88ec1b2976ef3d22a292f498518251421b782
Timestamp: 1743848815 Timestamp [UCT]: 2025-04-05 10:26:55 Age [y:d:h:m:s]: 00:229:11:23:23
Block: 1254777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161735 RingCT/type: yes/0
Extra: 01c9f920bb040584f86fec472abac88ec1b2976ef3d22a292f498518251421b782021100000003a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d11e0ee14fa01a4c84bfbc94f02dc5459c2be4473de09fa860c17f846cb326f5 0.600000000000 1741858 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": 1254787, "vin": [ { "gen": { "height": 1254777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d11e0ee14fa01a4c84bfbc94f02dc5459c2be4473de09fa860c17f846cb326f5" } } ], "extra": [ 1, 201, 249, 32, 187, 4, 5, 132, 248, 111, 236, 71, 42, 186, 200, 142, 193, 178, 151, 110, 243, 210, 42, 41, 47, 73, 133, 24, 37, 20, 33, 183, 130, 2, 17, 0, 0, 0, 3, 162, 237, 1, 107, 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