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: ecbbf5901f1603f540aff446b55501f14699c05c8caa53d210b874328a3d4663
Tx prefix hash: ceca17d5d9d0e0c935bd7765004d02538f25027b094ecbcc95abd6be84ea650e
Tx public key: 11d8355a02e9debeed4786f1110a6c1560b6a1a9d19c77cb5b808ca6cf07aeac
| Timestamp: 1780687567 | Timestamp [UTC]: 2026-06-05 19:26:07 | Age [y:d:h:m:s]: 00:003:03:52:46 |
| Block: 5488 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2398 | RingCT/type: yes/0 |
| Extra: 0111d8355a02e9debeed4786f1110a6c1560b6a1a9d19c77cb5b808ca6cf07aeac020900000001e49593ff00 | ||
1 output(s) for total of 34.818065559105 HMNY
| stealth address | amount | amount idx | tag |
| 00: 32550186935ce8cb5c22765c77cb676166ccffd9d89abb7aeff8ff18a450cf13 | 34.818065559105 | 6927 of 0 | <7d> |
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": 5548,
"vin": [ {
"gen": {
"height": 5488
}
}
],
"vout": [ {
"amount": 34818065559105,
"target": {
"tagged_key": {
"key": "32550186935ce8cb5c22765c77cb676166ccffd9d89abb7aeff8ff18a450cf13",
"view_tag": "7d"
}
}
}
],
"extra": [ 1, 17, 216, 53, 90, 2, 233, 222, 190, 237, 71, 134, 241, 17, 10, 108, 21, 96, 182, 161, 169, 209, 156, 119, 203, 91, 128, 140, 166, 207, 7, 174, 172, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}