← previous blocknext block →recent activity
Analyzing
Block #107,814,394
18 transactions · 17 stateful · 2026-09-25 05:52:40 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,814,394 · 18 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
1w02w13w24w35w48w09w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
12 touches
15 conflicts
0xba522812…1f1f
0x34b655…2a6f
12 touches
15 conflicts
0x2130a548…c1de
0x34b655…2a6f
12 touches
15 conflicts
0xf369641d…cd00
0x34b655…2a6f
12 touches
15 conflicts
0xd59f6ed1…03eb
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x53477650…a57e
0xd32edf…ff58
9 touches
10 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 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity