← previous blocknext block →recent activity
Analyzing
Block #106,555,735
28 transactions · 26 stateful · 2026-09-20 20:14:00 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,555,735 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w412w013w114w015w116w217w218w319w425w426w527w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7013779…71d5
0x34b655…2a6f
12 touches
15 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
10 touches
10 conflicts
0x0463db49…5d05
0x34b655…2a6f
10 touches
10 conflicts
0x7462b8f2…6312
0x34b655…2a6f
10 touches
10 conflicts
0xe6bd730f…df95
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xed863ec8…90dc
0x1b6862…e19c
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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 0xe7013779b8…5671d5
Audit this contract →
← previous block·next block →recent activity