← previous blocknext block →recent activity
Analyzing
Block #106,924,237
29 transactions · 27 stateful · 2026-09-22 03:09:44 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.31
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,924,237 · 29 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
7w08w09w110w211w312w414w315w416w517w618w719w824w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xf7ae2120…d1d2
0x34b655…2a6f
12 touches
15 conflicts
0xd4230a60…bd13
0x34b655…2a6f
10 touches
10 conflicts
0xbbb93c5b…db1b
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity