Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68064905ce56eacce083c01c25f4b4609a01a4c719ee0ed1a335fa6802d6809f

Tx prefix hash: 1a6c59706114e502c65988a5623d2e159850d514de9e90ca7aced71ea165dac1
Tx public key: a51f48d1e9a4fc3f656542500694c99a786f5ea2726f14fb2b9b8d6f90511400
Timestamp: 1764772031 Timestamp [UCT]: 2025-12-03 14:27:11 Age [y:d:h:m:s]: 00:018:22:15:08
Block: 1425626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13532 RingCT/type: yes/0
Extra: 01a51f48d1e9a4fc3f656542500694c99a786f5ea2726f14fb2b9b8d6f9051140002110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d90903232edb56635e7ad9a9ed2ae2a272a9bc5e31c5b6688d2cbe96d28393ca 0.600000000000 1914291 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": 1425636, "vin": [ { "gen": { "height": 1425626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d90903232edb56635e7ad9a9ed2ae2a272a9bc5e31c5b6688d2cbe96d28393ca" } } ], "extra": [ 1, 165, 31, 72, 209, 233, 164, 252, 63, 101, 101, 66, 80, 6, 148, 201, 154, 120, 111, 94, 162, 114, 111, 20, 251, 43, 155, 141, 111, 144, 81, 20, 0, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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