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: 4430fbe4c5845c47f6d862e0d1a7e513584e79ab9c32c2a160cc564d8f301c0e
Tx prefix hash: 13e9008e8170eafebca79559de69f60b71b1dd1d5cce00bb960a18cf52ca7013
Tx public key: d0496dd92ff0c8248e708a0d50662a46d13331af49ac0dab3aa93167a8a0a47d
| Timestamp: 1780694338 | Timestamp [UTC]: 2026-06-05 21:18:58 | Age [y:d:h:m:s]: 00:003:04:16:59 |
| Block: 5932 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1954 | RingCT/type: yes/0 |
| Extra: 01d0496dd92ff0c8248e708a0d50662a46d13331af49ac0dab3aa93167a8a0a47d020900000001e49593ff00 | ||
1 output(s) for total of 34.788591888590 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0c7ab399122c64fce8fc36c5138b3f1acc91771d67c7d9996a8eee31524d1531 | 34.788591888590 | 7393 of 0 | <84> |
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": 5992,
"vin": [ {
"gen": {
"height": 5932
}
}
],
"vout": [ {
"amount": 34788591888590,
"target": {
"tagged_key": {
"key": "0c7ab399122c64fce8fc36c5138b3f1acc91771d67c7d9996a8eee31524d1531",
"view_tag": "84"
}
}
}
],
"extra": [ 1, 208, 73, 109, 217, 47, 240, 200, 36, 142, 112, 138, 13, 80, 102, 42, 70, 209, 51, 49, 175, 73, 172, 13, 171, 58, 169, 49, 103, 168, 160, 164, 125, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}