← previous blocknext block →recent activity
Analyzing
Block #106,567,791
27 transactions · 26 stateful · 2026-09-20 21:14:41 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,567,791 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w09w010w111w012w114w015w121w123w324w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07e1d521…fc32
0x34b655…2a6f
8 touches
6 conflicts
0x375b6201…9c1e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x4e7eb462…b2b0
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
6 conflicts on slot 0x07e1d52158…b8fc32
Audit this contract →
← previous block·next block →recent activity