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: aa7917cade29beed847529f66ce83bbad2ba3114129171ff29d0db6e719549a5
Tx prefix hash: f9a6343e27219a41d6a14764e0f95ca2ffb0deb6c486d5b193903f97ad7cb23f
Tx public key: d5ff866f2d8d544056317388ea90d1a33bcef2f7ab51b6a051d2e9196f521301
| Timestamp: 1779897417 | Timestamp [UTC]: 2026-05-27 15:56:57 | Age [y:d:h:m:s]: 00:012:08:26:12 |
| Block: 3114 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4772 | RingCT/type: yes/0 |
| Extra: 01d5ff866f2d8d544056317388ea90d1a33bcef2f7ab51b6a051d2e9196f52130102090000000226697be300 | ||
1 output(s) for total of 34.976080980783 HMNY
| stealth address | amount | amount idx | tag |
| 00: 420176f0656ac4991ffe46f80491c6e74632654d4c001f60fc6b3bb6331ed1f8 | 34.976080980783 | 3716 of 0 | <1b> |
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": 3174,
"vin": [ {
"gen": {
"height": 3114
}
}
],
"vout": [ {
"amount": 34976080980783,
"target": {
"tagged_key": {
"key": "420176f0656ac4991ffe46f80491c6e74632654d4c001f60fc6b3bb6331ed1f8",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 213, 255, 134, 111, 45, 141, 84, 64, 86, 49, 115, 136, 234, 144, 209, 163, 59, 206, 242, 247, 171, 81, 182, 160, 81, 210, 233, 25, 111, 82, 19, 1, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}