Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a093beb69641f7c3b6c3619fab5e6162016c2842a67f34a53d3ee30f9ca236c1

Tx prefix hash: 651dd3771984d379b27e641fb168d3eb3986c2bc12f2127f3ee76054ab34c263
Tx public key: 38ac6fad7e8909e31c70c252d96a09bd293996eee3b5c6a60eb536c5acdb4d5f
Timestamp: 1729656935 Timestamp [UCT]: 2024-10-23 04:15:35 Age [y:d:h:m:s]: 01:028:03:55:22
Block: 1137585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278523 RingCT/type: yes/0
Extra: 0138ac6fad7e8909e31c70c252d96a09bd293996eee3b5c6a60eb536c5acdb4d5f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2815f89636eb4e8e9ccf3ee80d0542eaed2b99a0870e2ad91e07538e4709d9b9 0.600000000000 1621104 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": 1137595, "vin": [ { "gen": { "height": 1137585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2815f89636eb4e8e9ccf3ee80d0542eaed2b99a0870e2ad91e07538e4709d9b9" } } ], "extra": [ 1, 56, 172, 111, 173, 126, 137, 9, 227, 28, 112, 194, 82, 217, 106, 9, 189, 41, 57, 150, 238, 227, 181, 198, 166, 14, 181, 54, 197, 172, 219, 77, 95, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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