Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bef5a27e02db89155f8f414180a762b12633e7af4fb26b144c1ef3c6f0fb79c

Tx prefix hash: 89ba55773bbfa4f6c2cf05add5af5747dab3d86de3943df3bc1445641418b2b5
Tx public key: 0bd45fac0d25ff35fcc7d571bffc89abe59cd3baf5eb1a6ec1b64319a1df720a
Timestamp: 1762928646 Timestamp [UCT]: 2025-11-12 06:24:06 Age [y:d:h:m:s]: 00:016:00:34:49
Block: 1410325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11477 RingCT/type: yes/0
Extra: 010bd45fac0d25ff35fcc7d571bffc89abe59cd3baf5eb1a6ec1b64319a1df720a0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9adb982260b8ea9ebac7742fbe9c900179f5e51f834df0d16019d82f7b5a1e2e 0.600000000000 1898776 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": 1410335, "vin": [ { "gen": { "height": 1410325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9adb982260b8ea9ebac7742fbe9c900179f5e51f834df0d16019d82f7b5a1e2e" } } ], "extra": [ 1, 11, 212, 95, 172, 13, 37, 255, 53, 252, 199, 213, 113, 191, 252, 137, 171, 229, 156, 211, 186, 245, 235, 26, 110, 193, 182, 67, 25, 161, 223, 114, 10, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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