← previous blocknext block →recent activity
Analyzing
Block #106,567,971
28 transactions · 27 stateful · 2026-09-20 21:15:35 UTC
Parallelism
43/100
Blocked
70%
Avg conflicts / tx
3.43
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,567,971 · 28 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w48w511w612w714w815w917w1018w1119w1220w1321w1422w1525w926w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3277870…f03e
0x34b655…2a6f
22 touches
55 conflicts
0x678dc413…10a5
0x34b655…2a6f
20 touches
45 conflicts
0xfe2577ac…677b
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xba1edffb…323e
0x34b655…2a6f
14 touches
21 conflicts
0x23b2399c…6e4b
0x34b655…2a6f
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x5d1ac445…5233
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
55 conflicts on slot 0xa327787048…81f03e
Audit this contract →
← previous block·next block →recent activity