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: 6107ac5b14766a7bc42199789406c675786ae821029e068d5919d1276afa6715
Tx prefix hash: d5b96efbac5e7f4d31a2ba54c13acfa4ca86776fa49e1c0e758cf9704caabeb2
Tx public key: 16339cc3c7cf2495f59ac3a0d61a89ae30cbc2c5b5652f85f15347a384e482ea
| Timestamp: 1780322680 | Timestamp [UTC]: 2026-06-01 14:04:40 | Age [y:d:h:m:s]: 00:007:09:14:13 |
| Block: 5006 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2880 | RingCT/type: yes/0 |
| Extra: 0116339cc3c7cf2495f59ac3a0d61a89ae30cbc2c5b5652f85f15347a384e482ea02090000000c26697be300 | ||
1 output(s) for total of 34.850090019562 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3adb800ba618b78f1b5e4601559dae1f5717d6e008a0d9ca8a1ef31769f127b1 | 34.850090019562 | 6379 of 0 | <f7> |
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": 5066,
"vin": [ {
"gen": {
"height": 5006
}
}
],
"vout": [ {
"amount": 34850090019562,
"target": {
"tagged_key": {
"key": "3adb800ba618b78f1b5e4601559dae1f5717d6e008a0d9ca8a1ef31769f127b1",
"view_tag": "f7"
}
}
}
],
"extra": [ 1, 22, 51, 156, 195, 199, 207, 36, 149, 245, 154, 195, 160, 214, 26, 137, 174, 48, 203, 194, 197, 181, 101, 47, 133, 241, 83, 71, 163, 132, 228, 130, 234, 2, 9, 0, 0, 0, 12, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}