← previous blocknext block →recent activity
Analyzing
Block #91,119,378
30 transactions · 23 stateful · 2026-07-28 17:38:31 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,119,378 · 30 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
1w02w15w26w012w013w114w215w116w219w322w323w424w426w127w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6847107a…f468
0xa6afd3…d132
6 touches
3 conflicts
0x989252a1…d812
0xa6afd3…d132
6 touches
3 conflicts
0x4efae872…6aa8
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xefcdf19725…1096a2
Audit this contract →
← previous block·next block →recent activity