← previous blocknext block →recent activity
Analyzing
Block #106,950,002
32 transactions · 29 stateful · 2026-09-22 05:19:25 UTC
Parallelism
69/100
Blocked
52%
Avg conflicts / tx
1.06
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,950,002 · 32 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
1w02w14w05w16w28w19w010w111w214w115w216w321w427w529w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a5dca8…326a
0x34b655…2a6f
10 touches
10 conflicts
0xbab4a787…5e6f
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd6071d1d…496b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x70986451…c6bd
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
10 conflicts on slot 0x34a5dca8c9…91326a
Audit this contract →
← previous block·next block →recent activity