← previous blocknext block →recent activity
Analyzing
Block #106,934,128
28 transactions · 26 stateful · 2026-09-22 03:59:30 UTC
Parallelism
71/100
Blocked
62%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,934,128 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w08w111w012w113w314w415w116w217w318w419w524w125w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2022ad83…5c07
0x34b655…2a6f
14 touches
21 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
10 touches
10 conflicts
0x51087f5a…61f7
0x34b655…2a6f
8 touches
6 conflicts
0x73a0005f…70a8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
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 0x2022ad83f0…445c07
Audit this contract →
← previous block·next block →recent activity