← previous blocknext block →recent activity
Analyzing
Block #106,933,977
27 transactions · 25 stateful · 2026-09-22 03:58:45 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1.7
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,933,977 · 27 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w211w312w213w315w416w517w618w719w821w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
16 touches
28 conflicts
0x3780a34a…b50a
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0x0463db49…5d05
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xf71016c7…5c7c
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xae76fcd2…d26a
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
28 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity