← previous blocknext block →recent activity
Analyzing
Block #91,297,627
19 transactions · 19 stateful · 2026-07-29 08:36:06 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,297,627 · 19 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
1w03w14w26w37w08w19w210w313w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7e28e55c…d05c
0x754704…b603
8 touches
6 conflicts
0x57d4fa9c…e2d8
0x754704…b603
8 touches
6 conflicts
0x00000000…0001
0x659bd0…a9da
8 touches
6 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0000
0x659bd0…a9da
8 touches
6 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
8 touches
6 conflicts
0xbcbf5d09…8bac
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity