← previous blocknext block →recent activity
Analyzing
Block #106,932,152
34 transactions · 34 stateful · 2026-09-22 03:49:34 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
2.18
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,932,152 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w29w312w213w314w415w516w620w523w826w927w1033w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec25545e…589b
0x34b655…2a6f
16 touches
28 conflicts
0x94e7f277…471b
0x34b655…2a6f
16 touches
28 conflicts
0x70986451…c6bd
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x251ee419…4404
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x8fb6bad3…adeb
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xec25545ed8…c1589b
Audit this contract →
← previous block·next block →recent activity