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: 2b9a824452180ee122e5829439bb3ddeb514f30eeb003f54ced0da27cf841f0b
Tx prefix hash: 56c6c5908091a426fc1b66f69e7863419daa7931ff5bc5e1657a09ee3c3b6b09
Tx public key: b9ce268b4b6ed42c3a7112099e44acb267982fbd430d869a7a66a18d1dddc124
| Timestamp: 1780685320 | Timestamp [UTC]: 2026-06-05 18:48:40 | Age [y:d:h:m:s]: 00:003:05:58:07 |
| Block: 5383 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2503 | RingCT/type: yes/0 |
| Extra: 01b9ce268b4b6ed42c3a7112099e44acb267982fbd430d869a7a66a18d1dddc124020900000001e49593ff00 | ||
1 output(s) for total of 34.825039333980 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3da9281e09bb7b0aed9d940ad4ece5fe88495022ec7a52018696c2fe5730dd00 | 34.825039333980 | 6818 of 0 | <a7> |
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": 5443,
"vin": [ {
"gen": {
"height": 5383
}
}
],
"vout": [ {
"amount": 34825039333980,
"target": {
"tagged_key": {
"key": "3da9281e09bb7b0aed9d940ad4ece5fe88495022ec7a52018696c2fe5730dd00",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 185, 206, 38, 139, 75, 110, 212, 44, 58, 113, 18, 9, 158, 68, 172, 178, 103, 152, 47, 189, 67, 13, 134, 154, 122, 102, 161, 141, 29, 221, 193, 36, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}