← previous blocknext block →recent activity
Analyzing
Block #106,379,815
16 transactions · 14 stateful · 2026-09-20 05:28:36 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,379,815 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w18w212w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba33378a…f1df
0x34b655…2a6f
6 touches
3 conflicts
0xc8cb0701…3926
0x34b655…2a6f
6 touches
3 conflicts
0xca92d069…9633
0x34b655…2a6f
4 touches
1 conflict
0x0eb80b70…301b
0x34b655…2a6f
4 touches
1 conflict
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0x564e36eb…6d6a
0x34b655…2a6f
4 touches
1 conflict
0x95063b48…269f
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
3 conflicts on slot 0xba33378abc…73f1df
Audit this contract →
← previous block·next block →recent activity