← previous blocknext block →recent activity
Analyzing
Block #91,255,457
21 transactions · 20 stateful · 2026-07-29 05:03:08 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,255,457 · 21 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
1w03w04w16w27w38w49w010w212w113w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x8727ada9…770d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x0ba91aa8…fdab
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad06
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
6 touches
3 conflicts
0xebbd51a8…2e65
0x34b655…2a6f
6 touches
3 conflicts
0x97c67486…27fe
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity