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: 5aaa5b73198d4a6967a5aa351461740599973689cfeae111aacf1a62ae145674
Tx prefix hash: 84965381786aec195af6af66e71ff886e517b4cb0a26aac89863b81784c6be5b
Tx public key: 4f6d632b334a56a46685d416e8d9f5ba4be1dbcd049cc11414a8b490045f00ed
| Timestamp: 1780686628 | Timestamp [UTC]: 2026-06-05 19:10:28 | Age [y:d:h:m:s]: 00:003:08:28:22 |
| Block: 5439 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2511 | RingCT/type: yes/0 |
| Extra: 014f6d632b334a56a46685d416e8d9f5ba4be1dbcd049cc11414a8b490045f00ed020900000001e49593ff00 | ||
1 output(s) for total of 34.821319813575 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0969cf75375309f3e5118c831397af3d76f7618b9fcb562a6fd207fa25a5649a | 34.821319813575 | 6878 of 0 | <b6> |
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": 5499,
"vin": [ {
"gen": {
"height": 5439
}
}
],
"vout": [ {
"amount": 34821319813575,
"target": {
"tagged_key": {
"key": "0969cf75375309f3e5118c831397af3d76f7618b9fcb562a6fd207fa25a5649a",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 79, 109, 99, 43, 51, 74, 86, 164, 102, 133, 212, 22, 232, 217, 245, 186, 75, 225, 219, 205, 4, 156, 193, 20, 20, 168, 180, 144, 4, 95, 0, 237, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}