← previous blocknext block →recent activity
Analyzing
Block #107,813,266
21 transactions · 20 stateful · 2026-09-25 05:46:59 UTC
Parallelism
57/100
Blocked
60%
Avg conflicts / tx
1.76
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,813,266 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w110w211w312w413w214w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc64d3656…0c1c
0x34b655…2a6f
12 touches
15 conflicts
0xba522812…1f1f
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xa23b9051…392f
0x34b655…2a6f
8 touches
6 conflicts
0x48203298…65cb
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x6d43ee99…bdda
0x1b6862…e19c
8 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
15 conflicts on slot 0xc64d3656b5…c50c1c
Audit this contract →
← previous block·next block →recent activity