← previous blocknext block →recent activity
Analyzing
Block #108,873,520
22 transactions · 17 stateful · 2026-09-28 22:46:49 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,873,520 · 22 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
1w02w13w06w07w19w010w111w213w315w116w219w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
10 touches
10 conflicts
0x2a8bc05a…0464
0x37db7f…ec7b
8 touches
6 conflicts
0xa93fef74…94b3
0x37db7f…ec7b
8 touches
6 conflicts
0xe3e67fe3…e754
0x37db7f…ec7b
8 touches
6 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
8 touches
6 conflicts
0x45885570…ed97
0x34b655…2a6f
8 touches
6 conflicts
0x63435b04…27de
0x34b655…2a6f
8 touches
6 conflicts
0x69523dd3…faa2
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 0x9fc6ea791d…ace2dc
Audit this contract →
← previous block·next block →recent activity