← previous blocknext block →recent activity
Analyzing
Block #106,215,653
29 transactions · 28 stateful · 2026-09-19 15:42:25 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
1.66
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,215,653 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w17w08w19w210w111w114w316w418w519w626w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf22f58…5939
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xb96a71d9…f95c
0x34b655…2a6f
10 touches
10 conflicts
0x2c2761c0…476e
0x34b655…2a6f
8 touches
6 conflicts
0xfbabb02d…af07
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x330a9b56…4ff0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
15 conflicts on slot 0xecf22f58ca…2c5939
Audit this contract →
← previous block·next block →recent activity