← previous blocknext block →recent activity
Analyzing
Block #108,275,920
22 transactions · 21 stateful · 2026-09-26 20:35:31 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,275,920 · 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
1w02w13w24w35w06w110w111w212w313w414w215w316w417w521w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x570bf5da…6a77
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x05cdc9b4…d6d3
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x0f28fb99…3d29
0x1b6862…e19c
8 touches
6 conflicts
0xc87e767e…4bba
0x34b655…2a6f
8 touches
6 conflicts
0xab41643c…f9bf
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 0x570bf5da2c…566a77
Audit this contract →
← previous block·next block →recent activity