Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edf4b083ad8305f81cd1a184d7801fddbacb50e6f6c2de5a9f5875b37611947b

Tx prefix hash: 1befaa4caaf05fb4c7552a04a5b2e65dcbb4930b7d6b344f8e26798fd5956232
Tx public key: 93ef768b6b49b4e4f014ef6bc368e6529fc4bd703150ef3fdb782afbd7e50213
Timestamp: 1749316590 Timestamp [UCT]: 2025-06-07 17:16:30 Age [y:d:h:m:s]: 00:165:21:13:39
Block: 1300064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116225 RingCT/type: yes/0
Extra: 0193ef768b6b49b4e4f014ef6bc368e6529fc4bd703150ef3fdb782afbd7e50213021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2676c6d834bce992e272a7847f53fe1b2069d8931be775e2fcb519357aa23632 0.600000000000 1787611 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": 1300074, "vin": [ { "gen": { "height": 1300064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2676c6d834bce992e272a7847f53fe1b2069d8931be775e2fcb519357aa23632" } } ], "extra": [ 1, 147, 239, 118, 139, 107, 73, 180, 228, 240, 20, 239, 107, 195, 104, 230, 82, 159, 196, 189, 112, 49, 80, 239, 63, 219, 120, 42, 251, 215, 229, 2, 19, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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