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: 3642f2847ba6b3748d1439ab1eb6a9c916a66748623bccc975d417ae55d87e5b
Tx prefix hash: f454e688b70d67db2e2b9bb1291e824a7196d4190f82d0bdbaec2308569d3cf3
Tx public key: dbc32069ec9f182c9c5aec503ad19a589c289a0f370d1565663de022fb388c16
| Timestamp: 1779875099 | Timestamp [UTC]: 2026-05-27 09:44:59 | Age [y:d:h:m:s]: 00:012:13:33:54 |
| Block: 2872 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5014 | RingCT/type: yes/0 |
| Extra: 01dbc32069ec9f182c9c5aec503ad19a589c289a0f370d1565663de022fb388c1602090000000126697be300 | ||
1 output(s) for total of 34.992228925085 HMNY
| stealth address | amount | amount idx | tag |
| 00: 13b66092144ec6c7aa2fbbbdfde2bb7c654e2644ee96ae8700ff142adf26c8b0 | 34.992228925085 | 3400 of 0 | <c0> |
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": 2932,
"vin": [ {
"gen": {
"height": 2872
}
}
],
"vout": [ {
"amount": 34992228925085,
"target": {
"tagged_key": {
"key": "13b66092144ec6c7aa2fbbbdfde2bb7c654e2644ee96ae8700ff142adf26c8b0",
"view_tag": "c0"
}
}
}
],
"extra": [ 1, 219, 195, 32, 105, 236, 159, 24, 44, 156, 90, 236, 80, 58, 209, 154, 88, 156, 40, 154, 15, 55, 13, 21, 101, 102, 61, 224, 34, 251, 56, 140, 22, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}