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: 5d90d4beb5a560eee208cc6ad4f1c744799db3bb5c787af54c8766e96c64dd11
Tx prefix hash: b2e1e95917387d80a723a4f7734c8d01b142565811f6ac2ffa2ac32c9cc4a248
Tx public key: 11ea93fde8c407091fd0cfc1f6d4fb8641e0dcf42242fd9270b896f21eb40529
| Timestamp: 1780690447 | Timestamp [UTC]: 2026-06-05 20:14:07 | Age [y:d:h:m:s]: 00:003:05:21:50 |
| Block: 5662 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2224 | RingCT/type: yes/0 |
| Extra: 0111ea93fde8c407091fd0cfc1f6d4fb8641e0dcf42242fd9270b896f21eb40529020900000001e49593ff00 | ||
1 output(s) for total of 34.806512092352 HMNY
| stealth address | amount | amount idx | tag |
| 00: e546c29589c832b09889b5e56c727ea8abda5271f8c87f9a58b55e6250c05a05 | 34.806512092352 | 7111 of 0 | <91> |
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": 5722,
"vin": [ {
"gen": {
"height": 5662
}
}
],
"vout": [ {
"amount": 34806512092352,
"target": {
"tagged_key": {
"key": "e546c29589c832b09889b5e56c727ea8abda5271f8c87f9a58b55e6250c05a05",
"view_tag": "91"
}
}
}
],
"extra": [ 1, 17, 234, 147, 253, 232, 196, 7, 9, 31, 208, 207, 193, 246, 212, 251, 134, 65, 224, 220, 244, 34, 66, 253, 146, 112, 184, 150, 242, 30, 180, 5, 41, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}