Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5965a427f557d1d153074d98a55916931a0b4d8a5ddd47adc69cd576abcf65ee

Tx prefix hash: b6a085389f6f62ee1120a43e128e636c03f2148286a461a2fd17dc99add8bc05
Tx public key: 0371bcc107df3c5c5c5f445868f68d89ad39ed8c849f61a9b9c395f11e830561
Timestamp: 1758099978 Timestamp [UCT]: 2025-09-17 09:06:18 Age [y:d:h:m:s]: 00:110:14:30:33
Block: 1370313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79218 RingCT/type: yes/0
Extra: 010371bcc107df3c5c5c5f445868f68d89ad39ed8c849f61a9b9c395f11e830561021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06e05da9383cbbdc7fae951c867ff4011f299ebfc0977c630bb1ab586d544159 0.600000000000 1858388 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": 1370323, "vin": [ { "gen": { "height": 1370313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06e05da9383cbbdc7fae951c867ff4011f299ebfc0977c630bb1ab586d544159" } } ], "extra": [ 1, 3, 113, 188, 193, 7, 223, 60, 92, 92, 95, 68, 88, 104, 246, 141, 137, 173, 57, 237, 140, 132, 159, 97, 169, 185, 195, 149, 241, 30, 131, 5, 97, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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