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: de14c0661f63bd8bc954c5a19b88feae85e9b0a0954b90148f5bfce606ddb2aa
Tx prefix hash: bc9d193e17333f116422e66fc3e7192ef620617251d7b33a39b03fb7b6e41ecb
Tx public key: 4d99409dfe5dfd930fda64aef16f8d05c08ab4d49f196f8e4bc7e68ab97878fa
| Timestamp: 1779854300 | Timestamp [UTC]: 2026-05-27 03:58:20 | Age [y:d:h:m:s]: 00:012:23:40:30 |
| Block: 2593 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5356 | RingCT/type: yes/0 |
| Extra: 014d99409dfe5dfd930fda64aef16f8d05c08ab4d49f196f8e4bc7e68ab97878fa02090000000326697be300 | ||
1 output(s) for total of 35.025431422369 HMNY
| stealth address | amount | amount idx | tag |
| 00: c3312cc0cde6c94d661d0a2e579d9c2faf9c07cb73aaa0e90a042991a38fce2d | 35.025431422369 | 3051 of 0 | <a8> |
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": 2653,
"vin": [ {
"gen": {
"height": 2593
}
}
],
"vout": [ {
"amount": 35025431422369,
"target": {
"tagged_key": {
"key": "c3312cc0cde6c94d661d0a2e579d9c2faf9c07cb73aaa0e90a042991a38fce2d",
"view_tag": "a8"
}
}
}
],
"extra": [ 1, 77, 153, 64, 157, 254, 93, 253, 147, 15, 218, 100, 174, 241, 111, 141, 5, 192, 138, 180, 212, 159, 25, 111, 142, 75, 199, 230, 138, 185, 120, 120, 250, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}