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: 163842c3563abfd24f91af51ed7bfebe2fc157ed34e4516cd2c3c0201f11051b
Tx prefix hash: 22c3c2223ea2db5f382615defd219f3a76a94f7fd778cb457524a44418acd676
Tx public key: dc6b5b4e1ddcbffe48cf823efc0f646753bdd5bbaa6623fffd96bccb4ce1c792
| Timestamp: 1780072212 | Timestamp [UTC]: 2026-05-29 16:30:12 | Age [y:d:h:m:s]: 00:010:09:05:45 |
| Block: 4656 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3230 | RingCT/type: yes/0 |
| Extra: 01dc6b5b4e1ddcbffe48cf823efc0f646753bdd5bbaa6623fffd96bccb4ce1c79202090000000226697be300 | ||
1 output(s) for total of 34.873362754049 HMNY
| stealth address | amount | amount idx | tag |
| 00: b30b1e7160eb17dece27d9ecb1ef58b05e0f0e6958c263c04a04c6e5e1d21db3 | 34.873362754049 | 5849 of 0 | <3d> |
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": 4716,
"vin": [ {
"gen": {
"height": 4656
}
}
],
"vout": [ {
"amount": 34873362754049,
"target": {
"tagged_key": {
"key": "b30b1e7160eb17dece27d9ecb1ef58b05e0f0e6958c263c04a04c6e5e1d21db3",
"view_tag": "3d"
}
}
}
],
"extra": [ 1, 220, 107, 91, 78, 29, 220, 191, 254, 72, 207, 130, 62, 252, 15, 100, 103, 83, 189, 213, 187, 170, 102, 35, 255, 253, 150, 188, 203, 76, 225, 199, 146, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}