Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d346e8a08a8c2361691925d5c140f942346bec6bd666d7d072e491d8c59bc0

Tx prefix hash: f83af06973ea177a67bdabb457ac7a8c403237854ffb94c8a8dea79d9f4fe5f1
Tx public key: f78a2309b2252516a8483da8d1ff9ce20b153e0dfbf1979d34ccc6d68f014273
Timestamp: 1755909765 Timestamp [UCT]: 2025-08-23 00:42:45 Age [y:d:h:m:s]: 00:095:14:27:43
Block: 1352342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68274 RingCT/type: yes/0
Extra: 01f78a2309b2252516a8483da8d1ff9ce20b153e0dfbf1979d34ccc6d68f014273021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d5ba4ea4bf589e0e44e0e1c7d34f75ab54fa3e0dcefafc083e60f0d5e4dd750 0.600000000000 1840305 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": 1352352, "vin": [ { "gen": { "height": 1352342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d5ba4ea4bf589e0e44e0e1c7d34f75ab54fa3e0dcefafc083e60f0d5e4dd750" } } ], "extra": [ 1, 247, 138, 35, 9, 178, 37, 37, 22, 168, 72, 61, 168, 209, 255, 156, 226, 11, 21, 62, 13, 251, 241, 151, 157, 52, 204, 198, 214, 143, 1, 66, 115, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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