← previous blocknext block →recent activity
Analyzing
Block #107,642,442
17 transactions · 15 stateful · 2026-09-24 15:25:46 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,642,442 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e360a5d…8836
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0xf8b7e65f…2816
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xaf7f13f9…a2c9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb83
0x1b6862…e19c
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x6e360a5dec…698836
Audit this contract →
← previous block·next block →recent activity