Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a988a60222f1de0bbeffe95ecc8ef01a31ec531607cbbf2a4901f759444b9ef1

Tx prefix hash: 0e02eacf4660fa1f5ee6f1de30ed17dcfc533a5c08911a4c671d0b60fe71ab15
Tx public key: b899f9d95fe76a6209e86886e7b3c6d0005469ff6095c1e28bda9d451d876141
Timestamp: 1755828995 Timestamp [UCT]: 2025-08-22 02:16:35 Age [y:d:h:m:s]: 00:088:15:33:54
Block: 1351677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63295 RingCT/type: yes/0
Extra: 01b899f9d95fe76a6209e86886e7b3c6d0005469ff6095c1e28bda9d451d876141021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b64aaef1f5fb99fddebe8996ef8ee7a2de4117a121b621909b5443de75d39b99 0.600000000000 1839634 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": 1351687, "vin": [ { "gen": { "height": 1351677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b64aaef1f5fb99fddebe8996ef8ee7a2de4117a121b621909b5443de75d39b99" } } ], "extra": [ 1, 184, 153, 249, 217, 95, 231, 106, 98, 9, 232, 104, 134, 231, 179, 198, 208, 0, 84, 105, 255, 96, 149, 193, 226, 139, 218, 157, 69, 29, 135, 97, 65, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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