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: 54b48de46c2c278dc91dc1274f79d0cd6ca3a59aaa0b72ebc346b818e790f310
Tx prefix hash: 3c22c1bb00e3a024a4e98028045cda3d47b563d039fd77c67437e9ede8b4dfa7
Tx public key: 476160aa28706d96360a78bb6794fb768da8080be043a47ab693fcb0f29197dd
| Timestamp: 1780751618 | Timestamp [UTC]: 2026-06-06 13:13:38 | Age [y:d:h:m:s]: 00:002:12:22:19 |
| Block: 6496 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1390 | RingCT/type: yes/0 |
| Extra: 01476160aa28706d96360a78bb6794fb768da8080be043a47ab693fcb0f29197dd020900000005e49593ff00 | ||
1 output(s) for total of 34.751188333992 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7946cc543964e7bc85e39fe78b5f1563df847b4c3065746ec33b66ab68ef4056 | 34.751188333992 | 7993 of 0 | <c6> |
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": 6556,
"vin": [ {
"gen": {
"height": 6496
}
}
],
"vout": [ {
"amount": 34751188333992,
"target": {
"tagged_key": {
"key": "7946cc543964e7bc85e39fe78b5f1563df847b4c3065746ec33b66ab68ef4056",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 71, 97, 96, 170, 40, 112, 109, 150, 54, 10, 120, 187, 103, 148, 251, 118, 141, 168, 8, 11, 224, 67, 164, 122, 182, 147, 252, 176, 242, 145, 151, 221, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}