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: 468e009a40b6565d319e89edd488982e310d2ba6837cff4916a2e9cbb23281b2
Tx prefix hash: beae66b2678cc0eed1773ac26ba307795ca9d67a5c32418b246f81993aac78ab
Tx public key: 8e58c9ab94454768a17a517b2d624c1a8f9b96e8b7393eef5b552bff0b352bc2
| Timestamp: 1780686803 | Timestamp [UTC]: 2026-06-05 19:13:23 | Age [y:d:h:m:s]: 00:003:21:55:40 |
| Block: 5446 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3289 | RingCT/type: yes/0 |
| Extra: 018e58c9ab94454768a17a517b2d624c1a8f9b96e8b7393eef5b552bff0b352bc2020900000001e49593ff00 | ||
1 output(s) for total of 34.820854901458 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8e6322a852e123ab5099a47a3c93e7ebd08a72e3ec419f552f5798db0ace31fb | 34.820854901458 | 6885 of 0 | <55> |
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": 5506,
"vin": [ {
"gen": {
"height": 5446
}
}
],
"vout": [ {
"amount": 34820854901458,
"target": {
"tagged_key": {
"key": "8e6322a852e123ab5099a47a3c93e7ebd08a72e3ec419f552f5798db0ace31fb",
"view_tag": "55"
}
}
}
],
"extra": [ 1, 142, 88, 201, 171, 148, 69, 71, 104, 161, 122, 81, 123, 45, 98, 76, 26, 143, 155, 150, 232, 183, 57, 62, 239, 91, 85, 43, 255, 11, 53, 43, 194, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}