Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c2427a1c8df5dc06b2020756682d5e152ef8deea7ca929b57fcb4836f9bb01

Tx prefix hash: 2c6d51bee112d6dbbb6a6cb4cfecef887b84fec8dc000f5e375bb1e2c2753dc3
Tx public key: e7e5c5ac47a5afe1743c920b1abe7a5d62aed4edce4d982b4b4ed35fedb86ef1
Timestamp: 1755495601 Timestamp [UCT]: 2025-08-18 05:40:01 Age [y:d:h:m:s]: 00:089:11:00:45
Block: 1348993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63790 RingCT/type: yes/0
Extra: 01e7e5c5ac47a5afe1743c920b1abe7a5d62aed4edce4d982b4b4ed35fedb86ef1021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea69e627b8a0af3db6fe3e55d4dc158bcd6f21a10439a58f021549f092928ad8 0.600000000000 1836922 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": 1349003, "vin": [ { "gen": { "height": 1348993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea69e627b8a0af3db6fe3e55d4dc158bcd6f21a10439a58f021549f092928ad8" } } ], "extra": [ 1, 231, 229, 197, 172, 71, 165, 175, 225, 116, 60, 146, 11, 26, 190, 122, 93, 98, 174, 212, 237, 206, 77, 152, 43, 75, 78, 211, 95, 237, 184, 110, 241, 2, 17, 0, 0, 0, 4, 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