← previous blocknext block →recent activity
Analyzing
Block #108,278,691
24 transactions · 23 stateful · 2026-09-26 20:49:29 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,278,691 · 24 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
2w03w15w26w37w08w09w110w211w312w413w519w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97620bb8…d40a
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
8 touches
6 conflicts
0x775a8ad3…8307
0x34b655…2a6f
8 touches
6 conflicts
0x90affd2f…be9f
0x34b655…2a6f
8 touches
6 conflicts
0xaba6578d…bd48
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
21 conflicts on slot 0x97620bb810…ddd40a
Audit this contract →
← previous block·next block →recent activity