Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a0ec5bfd5c9940a33f0410240ca1a7cffd04c725a5245383d8c7eadf22d86c

Tx prefix hash: c312fab11cd1011a5339e0caa15ec4344adcc93fc8f70c7beb284f8f4a4292a2
Tx public key: 2edb607cfd0930142409341ce92edfc6fae3e781102d92c3c85248bad1360b0d
Timestamp: 1729773675 Timestamp [UCT]: 2024-10-24 12:41:15 Age [y:d:h:m:s]: 00:089:11:12:27
Block: 1138541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63935 RingCT/type: yes/0
Extra: 012edb607cfd0930142409341ce92edfc6fae3e781102d92c3c85248bad1360b0d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f4f1b80dcb13c220c78540c239a09fb4e4624b1fc5652d922d7eef75615a2fe 0.600000000000 1622226 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": 1138551, "vin": [ { "gen": { "height": 1138541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f4f1b80dcb13c220c78540c239a09fb4e4624b1fc5652d922d7eef75615a2fe" } } ], "extra": [ 1, 46, 219, 96, 124, 253, 9, 48, 20, 36, 9, 52, 28, 233, 46, 223, 198, 250, 227, 231, 129, 16, 45, 146, 195, 200, 82, 72, 186, 209, 54, 11, 13, 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