← previous blocknext block →recent activity
Analyzing
Block #106,215,847
20 transactions · 20 stateful · 2026-09-19 15:43:23 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,215,847 · 20 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
1w02w13w04w05w16w27w38w110w215w116w217w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2f3d969…79ad
0x34b655…2a6f
8 touches
6 conflicts
0x2e90dcf9…1289
0x34b655…2a6f
8 touches
6 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
6 touches
3 conflicts
0xb17fc29f…bfad
0x34b655…2a6f
6 touches
3 conflicts
0x9ac040c1…8226
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3a82529f…f8ba
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 0xb2f3d96925…7d79ad
Audit this contract →
← previous block·next block →recent activity