Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e483292f145a6b230b9e7c6903665a760c510c2a09143888afa28f5cc56b57f

Tx prefix hash: 437c08658ae14d373d3dbd33eb42ce79f833333630b22a1ad7ce6ff2d4e1bb71
Tx public key: 8dc3dada6ab5060239877c24f33cd55a1ce4d9d9af2e652f7b87db0ce4eb78a9
Timestamp: 1749915814 Timestamp [UCT]: 2025-06-14 15:43:34 Age [y:d:h:m:s]: 00:158:00:10:41
Block: 1304933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110690 RingCT/type: yes/0
Extra: 018dc3dada6ab5060239877c24f33cd55a1ce4d9d9af2e652f7b87db0ce4eb78a9021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb37a8ccd3bab71055644c2653e493287c881d736e882bfe0c80d54e0c7386f4 0.600000000000 1792528 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": 1304943, "vin": [ { "gen": { "height": 1304933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb37a8ccd3bab71055644c2653e493287c881d736e882bfe0c80d54e0c7386f4" } } ], "extra": [ 1, 141, 195, 218, 218, 106, 181, 6, 2, 57, 135, 124, 36, 243, 60, 213, 90, 28, 228, 217, 217, 175, 46, 101, 47, 123, 135, 219, 12, 228, 235, 120, 169, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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