Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e03f66ee81cea0263623d6b1fcc53a7d96172255d182ebb3be3e70c4d5485c2a

Tx prefix hash: a66879af8d30622f6310592083193a894918b4474786b0e0852bcf0c9d2d2e10
Tx public key: 0a7eeab4abe3bd11cbad2ab2f6a5a221f3d1e7100749011fca7394660d5727f4
Timestamp: 1750281308 Timestamp [UCT]: 2025-06-18 21:15:08 Age [y:d:h:m:s]: 00:154:10:46:21
Block: 1307895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108211 RingCT/type: yes/0
Extra: 010a7eeab4abe3bd11cbad2ab2f6a5a221f3d1e7100749011fca7394660d5727f4021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 508b1af5fca668c11b558b76cc96971d09b2b64a7e72f4e6076144e0f524b701 0.600000000000 1795506 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": 1307905, "vin": [ { "gen": { "height": 1307895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "508b1af5fca668c11b558b76cc96971d09b2b64a7e72f4e6076144e0f524b701" } } ], "extra": [ 1, 10, 126, 234, 180, 171, 227, 189, 17, 203, 173, 42, 178, 246, 165, 162, 33, 243, 209, 231, 16, 7, 73, 1, 31, 202, 115, 148, 102, 13, 87, 39, 244, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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