← previous blocknext block →recent activity
Analyzing
Block #106,955,910
28 transactions · 27 stateful · 2026-09-22 05:49:09 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,955,910 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w09w010w111w212w113w318w019w420w525w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf276c59d…b1fa
0x34b655…2a6f
12 touches
15 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
10 touches
10 conflicts
0x71ecf7c5…8b1e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbdae098f…b46d
0xd32edf…ff58
7 touches
6 conflicts
0x17a7f697…dcb7
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0xf276c59d77…adb1fa
Audit this contract →
← previous block·next block →recent activity