Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a12dd4cd4ddf9a0e80359b5410f2ac46f90a7e23cb7622a5d918405e4c0474de

Tx prefix hash: fbb9e8a3ce5e6a64767882b66a33807cd90982847eaf58d177037b0334dfe203
Tx public key: 266f97b712904e4c31c9b84069b66a1bafd451f4c4f194433feba59f08df68ff
Timestamp: 1756063832 Timestamp [UCT]: 2025-08-24 19:30:32 Age [y:d:h:m:s]: 00:093:19:20:39
Block: 1353623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66981 RingCT/type: yes/0
Extra: 01266f97b712904e4c31c9b84069b66a1bafd451f4c4f194433feba59f08df68ff0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b04bd18e945446d90d7f8fb733b6542da5578b7f137b55fdafe9ae348d48d568 0.600000000000 1841600 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": 1353633, "vin": [ { "gen": { "height": 1353623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b04bd18e945446d90d7f8fb733b6542da5578b7f137b55fdafe9ae348d48d568" } } ], "extra": [ 1, 38, 111, 151, 183, 18, 144, 78, 76, 49, 201, 184, 64, 105, 182, 106, 27, 175, 212, 81, 244, 196, 241, 148, 67, 63, 235, 165, 159, 8, 223, 104, 255, 2, 17, 0, 0, 0, 1, 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