← previous blocknext block →recent activity
Analyzing
Block #107,814,365
26 transactions · 25 stateful · 2026-09-25 05:52:31 UTC
Parallelism
62/100
Blocked
68%
Avg conflicts / tx
2.15
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,814,365 · 26 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
1w02w13w24w35w46w511w012w113w214w315w416w518w719w820w922w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
16 touches
28 conflicts
0xaa645624…7ea9
0x34b655…2a6f
16 touches
28 conflicts
0x2130a548…c1de
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x91945265…e592
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x7da7cd4f…cff9
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
10 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
28 conflicts on slot 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity