← previous blocknext block →recent activity
Analyzing
Block #106,186,833
21 transactions · 21 stateful · 2026-09-19 13:17:19 UTC
Parallelism
62/100
Blocked
71%
Avg conflicts / tx
1.86
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,186,833 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w510w611w712w315w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee64690f…0799
0x34b655…2a6f
16 touches
28 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
16 touches
28 conflicts
0xd597209e…9800
0x34b655…2a6f
10 touches
10 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
10 touches
10 conflicts
0x74200327…23ac
0x34b655…2a6f
8 touches
6 conflicts
0xa499e820…5b2d
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
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
28 conflicts on slot 0xee64690f56…6f0799
Audit this contract →
← previous block·next block →recent activity