Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa28a06ab56dbbb01fdb922a67421dd09353a6162d29f67426d392920dcf7e7c

Tx prefix hash: 2c9e3cdd88485a9e7cf7fd26c336010c4974a16ddc873f08b8eea115b5727d4b
Tx public key: 596d268a71b69f2440d157446dc9647ae8dc7a8a34907fef77b2011d2a0135e5
Timestamp: 1745343934 Timestamp [UCT]: 2025-04-22 17:45:34 Age [y:d:h:m:s]: 00:213:03:34:44
Block: 1267152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150062 RingCT/type: yes/0
Extra: 01596d268a71b69f2440d157446dc9647ae8dc7a8a34907fef77b2011d2a0135e5021100000006dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 968182d405c0953f8964b61dbaa754ae562b477403826c0aa2e345b40f295deb 0.600000000000 1754379 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": 1267162, "vin": [ { "gen": { "height": 1267152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "968182d405c0953f8964b61dbaa754ae562b477403826c0aa2e345b40f295deb" } } ], "extra": [ 1, 89, 109, 38, 138, 113, 182, 159, 36, 64, 209, 87, 68, 109, 201, 100, 122, 232, 220, 122, 138, 52, 144, 127, 239, 119, 178, 1, 29, 42, 1, 53, 229, 2, 17, 0, 0, 0, 6, 219, 181, 113, 193, 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