Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea35cc2f662674281e89507d4c42098f408bb2b89b4b1b3fcc26d9d868443af

Tx prefix hash: e2924b1717690816e83255eb1d597d499e6935a0816c0fb8efd368ab1d216be1
Tx public key: 85c4da4aada0f6e9281c0128c4046af91ae4b1097a19743e449b0f7fb88c6284
Timestamp: 1672944212 Timestamp [UCT]: 2023-01-05 18:43:32 Age [y:d:h:m:s]: 02:005:20:39:10
Block: 668305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526093 RingCT/type: yes/0
Extra: 0185c4da4aada0f6e9281c0128c4046af91ae4b1097a19743e449b0f7fb88c62840211000000075029cbac000000000000000000

1 output(s) for total of 3.746520110000 dcy

stealth address amount amount idx
00: 1f05629280c8f5d2ed60fdae790abe3987aa39a92cf58d7d65d7fec545afbf79 3.746520110000 1109546 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": 668315, "vin": [ { "gen": { "height": 668305 } } ], "vout": [ { "amount": 3746520110, "target": { "key": "1f05629280c8f5d2ed60fdae790abe3987aa39a92cf58d7d65d7fec545afbf79" } } ], "extra": [ 1, 133, 196, 218, 74, 173, 160, 246, 233, 40, 28, 1, 40, 196, 4, 106, 249, 26, 228, 177, 9, 122, 25, 116, 62, 68, 155, 15, 127, 184, 140, 98, 132, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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