Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3d011f53013fb0b9a42039901f35989196c347a8e55da100290be6eb2d6651

Tx prefix hash: 2c809285424d4fe309dee147845fc717368a465098faa93f22d2f14b2843f216
Tx public key: 78ac091c16e80654be224ad5290e9cb389447b7fb7d1df98957eebe9b1aca2fa
Timestamp: 1752954022 Timestamp [UCT]: 2025-07-19 19:40:22 Age [y:d:h:m:s]: 00:124:21:15:20
Block: 1329034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88045 RingCT/type: yes/0
Extra: 0178ac091c16e80654be224ad5290e9cb389447b7fb7d1df98957eebe9b1aca2fa021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2fd687d72e69fee477038be1f85d3536729c9e6bbfdd5c3291ca8a1e5db53a4 0.600000000000 1816809 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": 1329044, "vin": [ { "gen": { "height": 1329034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2fd687d72e69fee477038be1f85d3536729c9e6bbfdd5c3291ca8a1e5db53a4" } } ], "extra": [ 1, 120, 172, 9, 28, 22, 232, 6, 84, 190, 34, 74, 213, 41, 14, 156, 179, 137, 68, 123, 127, 183, 209, 223, 152, 149, 126, 235, 233, 177, 172, 162, 250, 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