For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 3d3a808430c46e39225214ff7cdde8c674f80925610d63a2ab91212d80aaa492
Tx prefix hash: 8a71c9b3d261897fe27ce841a7cdb40b56ca16e34bf5aa96ce96f0dce46d5b99
Tx public key: cd882258efcea25b8e913cdc51cf01d311651aecb866410257d1824d06373edd
| Timestamp: 1779725013 | Timestamp [UTC]: 2026-05-25 16:03:33 | Age [y:d:h:m:s]: 00:014:10:46:15 |
| Block: 1843 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6056 | RingCT/type: yes/0 |
| Extra: 01cd882258efcea25b8e913cdc51cf01d311651aecb866410257d1824d06373edd020900000002ba6d17be00 | ||
1 output(s) for total of 35.060974339595 HMNY
| stealth address | amount | amount idx | tag |
| 00: b20635468e3b3edaae9a57b57af2c75ca309e6040eaa49eaeafe70dbd428297f | 35.060974339595 | 2039 of 0 | <d7> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 1903,
"vin": [ {
"gen": {
"height": 1843
}
}
],
"vout": [ {
"amount": 35060974339595,
"target": {
"tagged_key": {
"key": "b20635468e3b3edaae9a57b57af2c75ca309e6040eaa49eaeafe70dbd428297f",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 205, 136, 34, 88, 239, 206, 162, 91, 142, 145, 60, 220, 81, 207, 1, 211, 17, 101, 26, 236, 184, 102, 65, 2, 87, 209, 130, 77, 6, 55, 62, 221, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}