← previous blocknext block →recent activity
Analyzing
Block #107,442,644
25 transactions · 24 stateful · 2026-09-23 22:39:29 UTC
Parallelism
68/100
Blocked
75%
Avg conflicts / tx
1.96
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,442,644 · 25 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
1w02w13w24w35w06w17w08w19w210w111w312w414w515w617w418w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x189fbafb…47ca
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x26565636…d21a
0x34b655…2a6f
12 touches
15 conflicts
0xc253b458…7933
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x485d2778…aa61
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
28 conflicts on slot 0x189fbafb46…d347ca
Audit this contract →
← previous block·next block →recent activity