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: e2cd60f1d0bf19dbdee41d0cbce8b4f805f25a2ab5123aa6c94bac1a5470093f
Tx prefix hash: 489a878ad8492df0f68a888aa2302bc6a15d963c2bf3c153e62c4552871bf551
Tx public key: 9fd30ae64a9a6b1f1e667a4dc49fd7bda6cbfb924de62e4778df53fd1c5acd3d
| Timestamp: 1779939936 | Timestamp [UTC]: 2026-05-28 03:45:36 | Age [y:d:h:m:s]: 00:012:13:23:27 |
| Block: 3479 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5255 | RingCT/type: yes/0 |
| Extra: 019fd30ae64a9a6b1f1e667a4dc49fd7bda6cbfb924de62e4778df53fd1c5acd3d02090000000626697be300 | ||
1 output(s) for total of 34.951739704747 HMNY
| stealth address | amount | amount idx | tag |
| 00: c574e4e58655e5bd625bb432ee25ed12fe55d0a7a8c8d979af7f82d4d2808cc5 | 34.951739704747 | 4198 of 0 | <09> |
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": 3539,
"vin": [ {
"gen": {
"height": 3479
}
}
],
"vout": [ {
"amount": 34951739704747,
"target": {
"tagged_key": {
"key": "c574e4e58655e5bd625bb432ee25ed12fe55d0a7a8c8d979af7f82d4d2808cc5",
"view_tag": "09"
}
}
}
],
"extra": [ 1, 159, 211, 10, 230, 74, 154, 107, 31, 30, 102, 122, 77, 196, 159, 215, 189, 166, 203, 251, 146, 77, 230, 46, 71, 120, 223, 83, 253, 28, 90, 205, 61, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}