← previous blocknext block →recent activity
Analyzing
Block #106,586,250
29 transactions · 27 stateful · 2026-09-20 22:47:35 UTC
Parallelism
62/100
Blocked
59%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,586,250 · 29 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w011w012w118w219w320w421w522w523w624w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xef7928ed…7fd4
0xd32edf…ff58
11 touches
15 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
10 touches
10 conflicts
0xdf717eac…a7e8
0x34b655…2a6f
10 touches
10 conflicts
0x10b1245e…de66
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity