Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fe9d7195ddf76b6642f48c3e291123de8f0295326fcd0608f9980192d8def78

Tx prefix hash: 9882916c8660c828a6da387a83448727f9e1d08fd153f352301c4ef256f675cf
Tx public key: 7e82b2ca2c4f07e10ea6416e03267dc3f628974fc0696d1c794e84e13dbf3a0b
Timestamp: 1729347578 Timestamp [UCT]: 2024-10-19 14:19:38 Age [y:d:h:m:s]: 00:018:21:06:18
Block: 1135045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13443 RingCT/type: yes/0
Extra: 017e82b2ca2c4f07e10ea6416e03267dc3f628974fc0696d1c794e84e13dbf3a0b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10bf50db53b5c4faf847379cf379a13ea7f7d8c1b340f5dc7175c7399ef0677e 0.600000000000 1618374 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": 1135055, "vin": [ { "gen": { "height": 1135045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10bf50db53b5c4faf847379cf379a13ea7f7d8c1b340f5dc7175c7399ef0677e" } } ], "extra": [ 1, 126, 130, 178, 202, 44, 79, 7, 225, 14, 166, 65, 110, 3, 38, 125, 195, 246, 40, 151, 79, 192, 105, 109, 28, 121, 78, 132, 225, 61, 191, 58, 11, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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