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: 9ede448de6b9199a57410c712b91f6a1c1c3e071bb57cf9c7df212607301355b
Tx prefix hash: cae8153a80e0738cd0aef163c6c7185b32e1d1d1958117c02b60bf710c99c2b0
Tx public key: 4fc3a14a63fa658a11f6b66ad9704c8617f311a762a4e0fc8dcb0af32ae194a6
| Timestamp: 1780776595 | Timestamp [UTC]: 2026-06-06 20:09:55 | Age [y:d:h:m:s]: 00:002:03:08:58 |
| Block: 6723 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1163 | RingCT/type: yes/0 |
| Extra: 014fc3a14a63fa658a11f6b66ad9704c8617f311a762a4e0fc8dcb0af32ae194a6020900000001e49593ff00 | ||
1 output(s) for total of 34.739565419069 HMNY
| stealth address | amount | amount idx | tag |
| 00: b6c10c85bbd20417136b984e1ac3c751f7304b682fa90903c33ead2954e98b91 | 34.739565419069 | 8293 of 0 | <5d> |
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": 6783,
"vin": [ {
"gen": {
"height": 6723
}
}
],
"vout": [ {
"amount": 34739565419069,
"target": {
"tagged_key": {
"key": "b6c10c85bbd20417136b984e1ac3c751f7304b682fa90903c33ead2954e98b91",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 79, 195, 161, 74, 99, 250, 101, 138, 17, 246, 182, 106, 217, 112, 76, 134, 23, 243, 17, 167, 98, 164, 224, 252, 141, 203, 10, 243, 42, 225, 148, 166, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}