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: 5f4dc53b38861e0139ff0301bd980e8583bb03127310aa55448b62085fa374bf
Tx prefix hash: de99ce7d1906c2bb517310959c80dbcecfb54295472f103851b2d6f4de85422b
Tx public key: 7a2557c19afcd3e23b49249cc0a9ec1d77a1ae993f90576d85cc40403ec551d1
| Timestamp: 1780694752 | Timestamp [UTC]: 2026-06-05 21:25:52 | Age [y:d:h:m:s]: 00:003:04:10:05 |
| Block: 5958 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1928 | RingCT/type: yes/0 |
| Extra: 017a2557c19afcd3e23b49249cc0a9ec1d77a1ae993f90576d85cc40403ec551d1020900000001e49593ff00 | ||
1 output(s) for total of 34.786866726419 HMNY
| stealth address | amount | amount idx | tag |
| 00: e21bff6c798773adcd4fa2756d833e3b453fc631b0b0aa2d335c5d8bb9496d54 | 34.786866726419 | 7421 of 0 | <0c> |
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": 6018,
"vin": [ {
"gen": {
"height": 5958
}
}
],
"vout": [ {
"amount": 34786866726419,
"target": {
"tagged_key": {
"key": "e21bff6c798773adcd4fa2756d833e3b453fc631b0b0aa2d335c5d8bb9496d54",
"view_tag": "0c"
}
}
}
],
"extra": [ 1, 122, 37, 87, 193, 154, 252, 211, 226, 59, 73, 36, 156, 192, 169, 236, 29, 119, 161, 174, 153, 63, 144, 87, 109, 133, 204, 64, 64, 62, 197, 81, 209, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}