← previous blocknext block →recent activity
Analyzing
Block #107,841,609
22 transactions · 19 stateful · 2026-09-25 08:09:38 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,841,609 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w110w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x508174fb…94d2
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xbf9df290…b04d
0x34b655…2a6f
10 touches
10 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
10 touches
10 conflicts
0x8f738079…ec23
0x1b6862…e19c
10 touches
10 conflicts
0x605fc4a2…4a6d
0xd32edf…ff58
9 touches
10 conflicts
0x80a3955c…5542
0x34b655…2a6f
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
10 conflicts on slot 0x508174fbc3…8094d2
Audit this contract →
← previous block·next block →recent activity