← previous blocknext block →recent activity
Analyzing
Block #107,823,153
24 transactions · 23 stateful · 2026-09-25 06:36:45 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,823,153 · 24 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
1w02w13w24w35w411w313w014w115w216w317w418w519w620w722w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
16 touches
28 conflicts
0xa92c5c48…c3e2
0x34b655…2a6f
12 touches
15 conflicts
0x4d42f16e…a6cd
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x923fbd2a…42f3
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x90a021f0…f922
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
28 conflicts on slot 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity