← previous blocknext block →recent activity
Analyzing
Block #91,248,153
25 transactions · 23 stateful · 2026-07-29 04:26:21 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,248,153 · 25 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
5w06w110w112w215w218w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x6dea4dbf…ba54
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x4015fc8d…554b
0x34b655…2a6f
6 touches
3 conflicts
0xdedb36e7…3585
0x34b655…2a6f
6 touches
3 conflicts
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity