Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2700feb1707cb47d99f9f8ad0ec880b0a91d4336f1846672a4d82633cf1fa0a

Tx prefix hash: e7b060ce90029f7bb726c002661c40e6d676d98e498cd953701f61fb4fa3fd44
Tx public key: 064264739c63383e117fc611995382b3f3b5cbfc531eee72937e3a79b6f0419e
Timestamp: 1676570336 Timestamp [UCT]: 2023-02-16 17:58:56 Age [y:d:h:m:s]: 02:265:04:16:22
Block: 698387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 708840 RingCT/type: yes/0
Extra: 01064264739c63383e117fc611995382b3f3b5cbfc531eee72937e3a79b6f0419e02110000000174b6d784000000000000000000

1 output(s) for total of 2.978200076000 dcy

stealth address amount amount idx
00: 705d46b19099b3877ffd091fccdc43e4eba1464bbdcaf65ea4110ce6a091b364 2.978200076000 1141684 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": 698397, "vin": [ { "gen": { "height": 698387 } } ], "vout": [ { "amount": 2978200076, "target": { "key": "705d46b19099b3877ffd091fccdc43e4eba1464bbdcaf65ea4110ce6a091b364" } } ], "extra": [ 1, 6, 66, 100, 115, 156, 99, 56, 62, 17, 127, 198, 17, 153, 83, 130, 179, 243, 181, 203, 252, 83, 30, 238, 114, 147, 126, 58, 121, 182, 240, 65, 158, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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