Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98a2a4df6e67aed2474c2b484acb6993bf0d535bf86780f8cb85b6f8f310460c

Tx prefix hash: 830e467659a492d5ac3f2d50d16cd58b7e366eb0a4a25de8380321f396966350
Tx public key: 526fc041df7133e519b5863ad612595b21f8fe300d92108f6dee75e224f8cdb3
Timestamp: 1694446262 Timestamp [UCT]: 2023-09-11 15:31:02 Age [y:d:h:m:s]: 01:066:13:27:23
Block: 845888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308863 RingCT/type: yes/0
Extra: 01526fc041df7133e519b5863ad612595b21f8fe300d92108f6dee75e224f8cdb302110000000575e3f0e9000000000000000000

1 output(s) for total of 0.966544767000 dcy

stealth address amount amount idx
00: 653ffe0396563039291ec5f4d108bab48f74e579ae0204c212033aaa5a8dc67e 0.966544767000 1299314 of 0

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": 845898, "vin": [ { "gen": { "height": 845888 } } ], "vout": [ { "amount": 966544767, "target": { "key": "653ffe0396563039291ec5f4d108bab48f74e579ae0204c212033aaa5a8dc67e" } } ], "extra": [ 1, 82, 111, 192, 65, 223, 113, 51, 229, 25, 181, 134, 58, 214, 18, 89, 91, 33, 248, 254, 48, 13, 146, 16, 143, 109, 238, 117, 226, 36, 248, 205, 179, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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