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: d31ecf8739abc1806480a6716da7dc5b078fb083c710642f8a26a60929e571fe
Tx prefix hash: d27702d670cdc64799d0bf24a3c1bf7328be9cdad532d37b83a9bbb89e6b4ec7
Tx public key: 40a0f700a3b50e82c2e63c37c5290e9a03672df9615d229f7174899354c5588c
| Timestamp: 1780065878 | Timestamp [UTC]: 2026-05-29 14:44:38 | Age [y:d:h:m:s]: 00:010:08:34:15 |
| Block: 4584 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3302 | RingCT/type: yes/0 |
| Extra: 0140a0f700a3b50e82c2e63c37c5290e9a03672df9615d229f7174899354c5588c02090000000126697be300 | ||
1 output(s) for total of 34.878152215050 HMNY
| stealth address | amount | amount idx | tag |
| 00: 48de7680b1e6758d36ac49b7281d615298a60abf69d6253ad55ad6d343afa45c | 34.878152215050 | 5754 of 0 | <7c> |
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": 4644,
"vin": [ {
"gen": {
"height": 4584
}
}
],
"vout": [ {
"amount": 34878152215050,
"target": {
"tagged_key": {
"key": "48de7680b1e6758d36ac49b7281d615298a60abf69d6253ad55ad6d343afa45c",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 64, 160, 247, 0, 163, 181, 14, 130, 194, 230, 60, 55, 197, 41, 14, 154, 3, 103, 45, 249, 97, 93, 34, 159, 113, 116, 137, 147, 84, 197, 88, 140, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}