← previous blocknext block →recent activity
Analyzing
Block #106,235,772
21 transactions · 17 stateful · 2026-09-19 17:23:43 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,235,772 · 21 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
2w04w15w011w212w313w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c6ff01…689f
0x34b655…2a6f
8 touches
6 conflicts
0xa81592a3…f569
0x34b655…2a6f
8 touches
6 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x55d48e94…6f58
0x34b655…2a6f
4 touches
1 conflict
0x2880d000…2d51
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
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
6 conflicts on slot 0x38c6ff017b…61689f
Audit this contract →
← previous block·next block →recent activity