Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aab186b7304fbb40ba1a2ea150f77d96061bf62f9bdc48d80054a10c043db7e

Tx prefix hash: a8a9d7ea1b0961aa090b6ad7232f0c5f895775382593b634e66f9a2c88c32715
Tx public key: 285e3e588fbfc1261eabffdd5d056c5591fc728d14f5d55324095d133e019111
Timestamp: 1756166152 Timestamp [UCT]: 2025-08-25 23:55:52 Age [y:d:h:m:s]: 00:126:21:50:35
Block: 1354467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90683 RingCT/type: yes/0
Extra: 01285e3e588fbfc1261eabffdd5d056c5591fc728d14f5d55324095d133e0191110211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c5a2f5854b4eebf4d9f2c1facd17d8ce1b793868907440fad9fdfc7af03ff41 0.600000000000 1842456 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": 1354477, "vin": [ { "gen": { "height": 1354467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c5a2f5854b4eebf4d9f2c1facd17d8ce1b793868907440fad9fdfc7af03ff41" } } ], "extra": [ 1, 40, 94, 62, 88, 143, 191, 193, 38, 30, 171, 255, 221, 93, 5, 108, 85, 145, 252, 114, 141, 20, 245, 213, 83, 36, 9, 93, 19, 62, 1, 145, 17, 2, 17, 0, 0, 0, 4, 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