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: 40b46bad033d293fac3ee85504d5274119ad9844b1f2ad558b2f3349ce76253e
Tx prefix hash: 9c47f76afbc884f1a02dfc1ee82be4a1f3176759c8efa1b7fd791c94211b3db0
Tx public key: e8854b88a5d1c538a173437c349bd6f291cc92d7fac43ee1d9e108798d3d8ada
| Timestamp: 1780692761 | Timestamp [UTC]: 2026-06-05 20:52:41 | Age [y:d:h:m:s]: 00:003:04:43:16 |
| Block: 5813 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2073 | RingCT/type: yes/0 |
| Extra: 01e8854b88a5d1c538a173437c349bd6f291cc92d7fac43ee1d9e108798d3d8ada020900000001e49593ff00 | ||
1 output(s) for total of 34.796488915107 HMNY
| stealth address | amount | amount idx | tag |
| 00: c8729e2c8933785e7e25705a3843925ddabe7a7534fb5ed75c822fca1aa354c1 | 34.796488915107 | 7270 of 0 | <e5> |
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": 5873,
"vin": [ {
"gen": {
"height": 5813
}
}
],
"vout": [ {
"amount": 34796488915107,
"target": {
"tagged_key": {
"key": "c8729e2c8933785e7e25705a3843925ddabe7a7534fb5ed75c822fca1aa354c1",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 232, 133, 75, 136, 165, 209, 197, 56, 161, 115, 67, 124, 52, 155, 214, 242, 145, 204, 146, 215, 250, 196, 62, 225, 217, 225, 8, 121, 141, 61, 138, 218, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}