← previous blocknext block →recent activity
Analyzing
Block #106,947,004
24 transactions · 24 stateful · 2026-09-22 05:04:19 UTC
Parallelism
58/100
Blocked
58%
Avg conflicts / tx
2.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,947,004 · 24 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
1w02w13w24w35w47w08w110w011w112w213w314w415w517w619w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaea7270e…770b
0x34b655…2a6f
18 touches
36 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x9375a764…dca1
0x34b655…2a6f
10 touches
10 conflicts
0xddf22357…0601
0xd32edf…ff58
9 touches
10 conflicts
0xd5a25205…645c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x155e52ca…fac7
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
36 conflicts on slot 0xaea7270ea9…c6770b
Audit this contract →
← previous block·next block →recent activity