Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ad2a1b666b553f048acd68e68468ce757edd693f30e4e2ecb4a41bbd176be1d

Tx prefix hash: e4c5ab66cb4fbf40ffe3201d9955901c271c600c7efedf581e61e632dc29365f
Tx public key: f5eae3cfee7dfdc60550d29bc12682ef2959c80087d731382e3f77f593fd39e7
Timestamp: 1747990716 Timestamp [UCT]: 2025-05-23 08:58:36 Age [y:d:h:m:s]: 00:246:02:23:04
Block: 1289083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173483 RingCT/type: yes/0
Extra: 01f5eae3cfee7dfdc60550d29bc12682ef2959c80087d731382e3f77f593fd39e70211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1737494b25e2c9b3c11eabc6ae43002f5dde28907d42f1f7059dad764e0bfc0 0.600000000000 1776550 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": 1289093, "vin": [ { "gen": { "height": 1289083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1737494b25e2c9b3c11eabc6ae43002f5dde28907d42f1f7059dad764e0bfc0" } } ], "extra": [ 1, 245, 234, 227, 207, 238, 125, 253, 198, 5, 80, 210, 155, 193, 38, 130, 239, 41, 89, 200, 0, 135, 215, 49, 56, 46, 63, 119, 245, 147, 253, 57, 231, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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