← previous blocknext block →recent activity
Analyzing
Block #91,248,993
15 transactions · 15 stateful · 2026-07-29 04:30:34 UTC
Parallelism
60/100
Blocked
60%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,248,993 · 15 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
3w04w15w26w27w38w39w310w011w412w514w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x539ac47f…eb6f
0x34b655…2a6f
6 touches
3 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x81561f70…fefd
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc3c56897…40c9
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
3 conflicts on slot 0xce06a0f7c4…61efef
Audit this contract →
← previous block·next block →recent activity