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: 795c6d7a7c76f23a64d9b4ca9a7ab25e66888626e95cf312e1c91677639c43d2
Tx prefix hash: 6ff90730c88c4ace785cf6fd1a63540e573f91a17b5893e8e6ec0553263ec3c6
Tx public key: 950a822ef1335a3bc4840c7ee10e930b66de8128830313c860711c33fbc5c775
| Timestamp: 1780990143 | Timestamp [UTC]: 2026-06-09 07:29:03 | Age [y:d:h:m:s]: 00:000:07:19:52 |
| Block: 8213 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 444 | RingCT/type: yes/0 |
| Extra: 01950a822ef1335a3bc4840c7ee10e930b66de8128830313c860711c33fbc5c775020900000001e49593ff00 | ||
1 output(s) for total of 34.637567098891 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6408de7851beace214998bd3e0a7d78f6df31c693057a490db1bb5049d15a7f4 | 34.637567098891 | 10167 of 0 | <e7> |
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": 8273,
"vin": [ {
"gen": {
"height": 8213
}
}
],
"vout": [ {
"amount": 34637567098891,
"target": {
"tagged_key": {
"key": "6408de7851beace214998bd3e0a7d78f6df31c693057a490db1bb5049d15a7f4",
"view_tag": "e7"
}
}
}
],
"extra": [ 1, 149, 10, 130, 46, 241, 51, 90, 59, 196, 132, 12, 126, 225, 14, 147, 11, 102, 222, 129, 40, 131, 3, 19, 200, 96, 113, 28, 51, 251, 197, 199, 117, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}