Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa9ce6706e07b59ab71c7c5555ce463d1d3773dba86dac0ed5e62b30cfba992e

Tx prefix hash: 90bef32d3a529e9ecab05a3fbfb4fd618db5026f3b476ce6b2614a9575d58f14
Tx public key: a0adca1f24b715ca0980d4ab15114b9f3cab0d5adc3028cbdbc776da1123ed1b
Timestamp: 1709054090 Timestamp [UCT]: 2024-02-27 17:14:50 Age [y:d:h:m:s]: 01:335:09:28:35
Block: 966819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498349 RingCT/type: yes/0
Extra: 01a0adca1f24b715ca0980d4ab15114b9f3cab0d5adc3028cbdbc776da1123ed1b0211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d5718ad753960a424b82880a12b01593fab39174be882ee6b408f66001cc9c0 0.600000000000 1426590 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": 966829, "vin": [ { "gen": { "height": 966819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d5718ad753960a424b82880a12b01593fab39174be882ee6b408f66001cc9c0" } } ], "extra": [ 1, 160, 173, 202, 31, 36, 183, 21, 202, 9, 128, 212, 171, 21, 17, 75, 159, 60, 171, 13, 90, 220, 48, 40, 203, 219, 199, 118, 218, 17, 35, 237, 27, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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