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: d2c2bc87f7a37ea2f44903e6cab152f7186143af0874b13e938e3252047f5e8b
Tx prefix hash: 2a21e77c1db6654c8d15534d6dc3e5fc474ba3180a8436c046064ba5b6d31de8
Tx public key: 482805cd06f4276c1b9eb1ec9c481f28a63de2ffc65ecdcba09c8708d6ac31d7
| Timestamp: 1780771576 | Timestamp [UTC]: 2026-06-06 18:46:16 | Age [y:d:h:m:s]: 00:006:16:16:00 |
| Block: 6670 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2075 | RingCT/type: yes/0 |
| Extra: 01482805cd06f4276c1b9eb1ec9c481f28a63de2ffc65ecdcba09c8708d6ac31d7020900000001e49593ff00 | ||
1 output(s) for total of 34.739657058702 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64667bf7a08993cc85dc11924cc33f4b934cc038715753331269654b75ce4934 | 34.739657058702 | 8226 of 0 | <6b> |
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": 6730,
"vin": [ {
"gen": {
"height": 6670
}
}
],
"vout": [ {
"amount": 34739657058702,
"target": {
"tagged_key": {
"key": "64667bf7a08993cc85dc11924cc33f4b934cc038715753331269654b75ce4934",
"view_tag": "6b"
}
}
}
],
"extra": [ 1, 72, 40, 5, 205, 6, 244, 39, 108, 27, 158, 177, 236, 156, 72, 31, 40, 166, 61, 226, 255, 198, 94, 205, 203, 160, 156, 135, 8, 214, 172, 49, 215, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}