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: 3a2d583324149b1ddcc243a918a91c668d4374570a95e199d3225b8e6c8d1a9c
Tx prefix hash: 08a995741c3394183a9c98de7ca3b93e7647df6cde9ee1687df98cd9d386afa9
Tx public key: dfdd5c80a1de56b47d8703b30fcadd9eafb621c101d5e68923face3d84913649
| Timestamp: 1779884613 | Timestamp [UTC]: 2026-05-27 12:23:33 | Age [y:d:h:m:s]: 00:012:15:15:17 |
| Block: 2994 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4948 | RingCT/type: yes/0 |
| Extra: 01dfdd5c80a1de56b47d8703b30fcadd9eafb621c101d5e68923face3d8491364902090000000226697be300 | ||
1 output(s) for total of 34.984087294262 HMNY
| stealth address | amount | amount idx | tag |
| 00: 159ae8e73d84d27a80fec0bcaac522f861271388ea44921a52b4084950c564c5 | 34.984087294262 | 3554 of 0 | <33> |
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": 3054,
"vin": [ {
"gen": {
"height": 2994
}
}
],
"vout": [ {
"amount": 34984087294262,
"target": {
"tagged_key": {
"key": "159ae8e73d84d27a80fec0bcaac522f861271388ea44921a52b4084950c564c5",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 223, 221, 92, 128, 161, 222, 86, 180, 125, 135, 3, 179, 15, 202, 221, 158, 175, 182, 33, 193, 1, 213, 230, 137, 35, 250, 206, 61, 132, 145, 54, 73, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}