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: bbb77ed06c772123145a243d6e05dea4fe0db3ef252699e2602b5d255fa99bf0
Tx prefix hash: 4a1e90168062fc9ba5dc74db92297c48c7340d68458e1a939cc8e5065b11e79c
Tx public key: 6111c84014570cf890912c80ce8a0317f1230f0268d2e93659d141b47467d1e5
| Timestamp: 1780688678 | Timestamp [UTC]: 2026-06-05 19:44:38 | Age [y:d:h:m:s]: 00:007:15:17:38 |
| Block: 5543 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3202 | RingCT/type: yes/0 |
| Extra: 016111c84014570cf890912c80ce8a0317f1230f0268d2e93659d141b47467d1e5020900000001e49593ff00 | ||
1 output(s) for total of 34.814413186764 HMNY
| stealth address | amount | amount idx | tag |
| 00: 979605c4ce540d95ec5a541273551504174f9bf16be6daee97c9602bd700d41a | 34.814413186764 | 6986 of 0 | <78> |
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": 5603,
"vin": [ {
"gen": {
"height": 5543
}
}
],
"vout": [ {
"amount": 34814413186764,
"target": {
"tagged_key": {
"key": "979605c4ce540d95ec5a541273551504174f9bf16be6daee97c9602bd700d41a",
"view_tag": "78"
}
}
}
],
"extra": [ 1, 97, 17, 200, 64, 20, 87, 12, 248, 144, 145, 44, 128, 206, 138, 3, 23, 241, 35, 15, 2, 104, 210, 233, 54, 89, 209, 65, 180, 116, 103, 209, 229, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}