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: e644405ff614df4487ef669a87c1da5d794f995b4f9d0daa10dd61c48fb82d2b
Tx prefix hash: 6ad2565f6bc70a9da717418c0c77ab8dde54b08c00ddf80d5d3571b02c7c3fbb
Tx public key: 09efa367d7cc4309df442a8dc04b6c0ef686321ef8cfa4fc29ed891beca3c443
| Timestamp: 1780806750 | Timestamp [UTC]: 2026-06-07 04:32:30 | Age [y:d:h:m:s]: 00:006:06:29:46 |
| Block: 6958 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1787 | RingCT/type: yes/0 |
| Extra: 0109efa367d7cc4309df442a8dc04b6c0ef686321ef8cfa4fc29ed891beca3c443020900000001e49593ff00 | ||
1 output(s) for total of 34.732806017303 HMNY
| stealth address | amount | amount idx | tag |
| 00: f701b849986cc8ccd995d84459b5eae8aa86dccbbd605dc74a94154fc5a27012 | 34.732806017303 | 8580 of 0 | <25> |
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": 7018,
"vin": [ {
"gen": {
"height": 6958
}
}
],
"vout": [ {
"amount": 34732806017303,
"target": {
"tagged_key": {
"key": "f701b849986cc8ccd995d84459b5eae8aa86dccbbd605dc74a94154fc5a27012",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 9, 239, 163, 103, 215, 204, 67, 9, 223, 68, 42, 141, 192, 75, 108, 14, 246, 134, 50, 30, 248, 207, 164, 252, 41, 237, 137, 27, 236, 163, 196, 67, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}