Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54d5dbeb71f9b784fd8c15d62121bb85e2a5a27576092d768640550db3fd9659

Tx prefix hash: c120eae95da5bcf9f0def7ae2a3ee38a05ddfe8131707545a5f77c9610fd7c41
Tx public key: c977649f9dcdc4eeae28ce78635779a941cd6351b3f60258fb15bf3134df09ec
Timestamp: 1762966359 Timestamp [UCT]: 2025-11-12 16:52:39 Age [y:d:h:m:s]: 00:052:22:47:47
Block: 1410642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37932 RingCT/type: yes/0
Extra: 01c977649f9dcdc4eeae28ce78635779a941cd6351b3f60258fb15bf3134df09ec021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b11830813044641f2eda26d46f6b79a9dc61a8e8b0db75d2f8008594a98ba1ad 0.600000000000 1899095 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": 1410652, "vin": [ { "gen": { "height": 1410642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b11830813044641f2eda26d46f6b79a9dc61a8e8b0db75d2f8008594a98ba1ad" } } ], "extra": [ 1, 201, 119, 100, 159, 157, 205, 196, 238, 174, 40, 206, 120, 99, 87, 121, 169, 65, 205, 99, 81, 179, 246, 2, 88, 251, 21, 191, 49, 52, 223, 9, 236, 2, 17, 0, 0, 0, 1, 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