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: 292632bd15d5fe37d16427586c5e90a3cabbb02eae3cf0b7c1431d96dae16741
Tx prefix hash: 3dc5b046d6db9aebd5dd7ad80a28634cff85356e8ba8d27a5d816b1510e4a5fe
Tx public key: 5f3405357ecbeb45c6976cdfe1b6e58794916f23151808f7e3dcdee04764e5dd
| Timestamp: 1780075951 | Timestamp [UTC]: 2026-05-29 17:32:31 | Age [y:d:h:m:s]: 00:010:08:03:26 |
| Block: 4702 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3184 | RingCT/type: yes/0 |
| Extra: 015f3405357ecbeb45c6976cdfe1b6e58794916f23151808f7e3dcdee04764e5dd02090000000326697be300 | ||
1 output(s) for total of 34.870303164959 HMNY
| stealth address | amount | amount idx | tag |
| 00: 779583ce97fcffe9f2f0ff530eee87667e9ffeddbc3807ce2e9d21f33ac8f064 | 34.870303164959 | 5908 of 0 | <de> |
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": 4762,
"vin": [ {
"gen": {
"height": 4702
}
}
],
"vout": [ {
"amount": 34870303164959,
"target": {
"tagged_key": {
"key": "779583ce97fcffe9f2f0ff530eee87667e9ffeddbc3807ce2e9d21f33ac8f064",
"view_tag": "de"
}
}
}
],
"extra": [ 1, 95, 52, 5, 53, 126, 203, 235, 69, 198, 151, 108, 223, 225, 182, 229, 135, 148, 145, 111, 35, 21, 24, 8, 247, 227, 220, 222, 224, 71, 100, 229, 221, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}