Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 77175a3f4c97e067faf931e3abb233ee7977f569c87913bc45098fa758858766

Tx prefix hash: 710d56d61a39a1e94257d04b74316f8306192fd8d419de644dc9acff7f4080a1
Tx public key: 2b1836c39d13a35f1a2617c71dc30ef44f43cc77f5c175dce341492b73ae829a
Timestamp: 1717768794 Timestamp [UCT]: 2024-06-07 13:59:54 Age [y:d:h:m:s]: 00:282:16:26:54
Block: 1039068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202019 RingCT/type: yes/0
Extra: 012b1836c39d13a35f1a2617c71dc30ef44f43cc77f5c175dce341492b73ae829a0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d76c3512866afce73002e6ef85cb1163c0f8d3c0469a7f2b04e907b152f4f40b 0.600000000000 1507657 of 15

Check which outputs belong to given Dinastycoin 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 Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-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": 1039078, "vin": [ { "gen": { "height": 1039068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d76c3512866afce73002e6ef85cb1163c0f8d3c0469a7f2b04e907b152f4f40b" } } ], "extra": [ 1, 43, 24, 54, 195, 157, 19, 163, 95, 26, 38, 23, 199, 29, 195, 14, 244, 79, 67, 204, 119, 245, 193, 117, 220, 227, 65, 73, 43, 115, 174, 130, 154, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8