Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7492637b37824d15521ca191bfd3e30b35b380a9686a195e19f38f0ea47c6764

Tx prefix hash: 44d1c4a1cb6a9a5f2cc062cca707511d6f58fc89dd691e26dc5fe5c22255f84d
Tx public key: 32aaee519261ff42551dac2f46f5ab84b88486f8b32e9a6c83d1dda8b33fb4fd
Timestamp: 1708683726 Timestamp [UCT]: 2024-02-23 10:22:06 Age [y:d:h:m:s]: 01:071:16:55:09
Block: 963739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312279 RingCT/type: yes/0
Extra: 0132aaee519261ff42551dac2f46f5ab84b88486f8b32e9a6c83d1dda8b33fb4fd0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2621f341ddba45ecebb04b3c7bda33f792884e0926ce81abcc2c26dd6892eab 0.600000000000 1423464 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": 963749, "vin": [ { "gen": { "height": 963739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2621f341ddba45ecebb04b3c7bda33f792884e0926ce81abcc2c26dd6892eab" } } ], "extra": [ 1, 50, 170, 238, 81, 146, 97, 255, 66, 85, 29, 172, 47, 70, 245, 171, 132, 184, 132, 134, 248, 179, 46, 154, 108, 131, 209, 221, 168, 179, 63, 180, 253, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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