Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c3a4469e132273740f32ce1cb1d034b69e0f8a0eb1bd498aba1b4cdb2a9bf0c

Tx prefix hash: 5f549cffe9f2bafb45797e3d6d6531ca5b16170154494ea0b1aab4598e2313ba
Tx public key: 3cfc46ee676c30168c9c825244ecc990e10e6c9998e6f94f45679eb297e97ee9
Timestamp: 1763306095 Timestamp [UCT]: 2025-11-16 15:14:55 Age [y:d:h:m:s]: 00:037:05:19:50
Block: 1413447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26654 RingCT/type: yes/0
Extra: 013cfc46ee676c30168c9c825244ecc990e10e6c9998e6f94f45679eb297e97ee9021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f5d4c899e23fb019589f6b32f8534d7555ab3673669e469720f6c88428c58d2 0.600000000000 1901926 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": 1413457, "vin": [ { "gen": { "height": 1413447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f5d4c899e23fb019589f6b32f8534d7555ab3673669e469720f6c88428c58d2" } } ], "extra": [ 1, 60, 252, 70, 238, 103, 108, 48, 22, 140, 156, 130, 82, 68, 236, 201, 144, 225, 14, 108, 153, 152, 230, 249, 79, 69, 103, 158, 178, 151, 233, 126, 233, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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