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: 8f8c709543b6314b7e931220fc0288e3aef3aca1db956296b8f735b4acbf0a03
Tx prefix hash: 1445b55919088e17969dddecd1195f90c1d181b6f5d705a16cdaed70b08c46c1
Tx public key: a50f5b0006f1072f83c5e9f7bdd5bbbcd7bd32e4b61b5b901a3b9fb3c3b04974
| Timestamp: 1780400685 | Timestamp [UTC]: 2026-06-02 11:44:45 | Age [y:d:h:m:s]: 00:006:13:51:12 |
| Block: 5280 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2606 | RingCT/type: yes/0 |
| Extra: 01a50f5b0006f1072f83c5e9f7bdd5bbbcd7bd32e4b61b5b901a3b9fb3c3b0497402090000000826697be300 | ||
1 output(s) for total of 34.831881632181 HMNY
| stealth address | amount | amount idx | tag |
| 00: c50d20d006b80dceab5ed0be42fc7a4476641f8dce160c5c7233b09706c91487 | 34.831881632181 | 6693 of 0 | <72> |
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": 5340,
"vin": [ {
"gen": {
"height": 5280
}
}
],
"vout": [ {
"amount": 34831881632181,
"target": {
"tagged_key": {
"key": "c50d20d006b80dceab5ed0be42fc7a4476641f8dce160c5c7233b09706c91487",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 165, 15, 91, 0, 6, 241, 7, 47, 131, 197, 233, 247, 189, 213, 187, 188, 215, 189, 50, 228, 182, 27, 91, 144, 26, 59, 159, 179, 195, 176, 73, 116, 2, 9, 0, 0, 0, 8, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}