← previous blocknext block →recent activity
Analyzing
Block #106,282,801
34 transactions · 31 stateful · 2026-09-19 21:20:23 UTC
Parallelism
71/100
Blocked
71%
Avg conflicts / tx
2.18
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,282,801 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w28w29w314w317w418w519w620w521w727w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
10 touches
10 conflicts
0xfbdb0c33…9449
0x34b655…2a6f
10 touches
10 conflicts
0x3b6e959d…158f
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity