← previous blocknext block →recent activity
Analyzing
Block #106,457,593
39 transactions · 37 stateful · 2026-09-20 12:00:05 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
2.64
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,457,593 · 39 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w726w828w929w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0262e1c6…52e1
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
12 touches
15 conflicts
0xa384061e…9f51
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x36d7075f…d5c9
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
36 conflicts on slot 0x0262e1c696…e752e1
Audit this contract →
← previous block·next block →recent activity