← previous blocknext block →recent activity
Analyzing
Block #107,848,565
23 transactions · 19 stateful · 2026-09-25 08:44:39 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,848,565 · 23 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
1w02w13w29w011w112w213w314w415w516w617w722w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf75c3a6b…0568
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xba522812…1f1f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x3af0dd8e…0028
0x1b6862…e19c
8 touches
6 conflicts
0xa0cbbfcc…3133
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x5144b409…f533
0xd32edf…ff58
7 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
6 conflicts on slot 0xf75c3a6bf5…da0568
Audit this contract →
← previous block·next block →recent activity