Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18c2035afcfec388828cf9e39d32cc398f99c9674c762945bf361f0da528ef96

Tx prefix hash: f642214777f7512db43c1ac1519f7f07d6cce65819c938d5916f8565730e3578
Tx public key: 4635b69fb130511435e0dd6a0d736bee43ca9ea53077a1146f3a30d4bc0551e8
Timestamp: 1685351989 Timestamp [UCT]: 2023-05-29 09:19:49 Age [y:d:h:m:s]: 01:275:08:03:03
Block: 770555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457958 RingCT/type: yes/0
Extra: 014635b69fb130511435e0dd6a0d736bee43ca9ea53077a1146f3a30d4bc0551e8021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.733132331000 dcy

stealth address amount amount idx
00: 25f5dc0c9bcf8c5647bb8ebf297a3c0bc9b8cca1e463c1db9915c2edffc283dc 1.733132331000 1219864 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": 770565, "vin": [ { "gen": { "height": 770555 } } ], "vout": [ { "amount": 1733132331, "target": { "key": "25f5dc0c9bcf8c5647bb8ebf297a3c0bc9b8cca1e463c1db9915c2edffc283dc" } } ], "extra": [ 1, 70, 53, 182, 159, 177, 48, 81, 20, 53, 224, 221, 106, 13, 115, 107, 238, 67, 202, 158, 165, 48, 119, 161, 20, 111, 58, 48, 212, 188, 5, 81, 232, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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