← previous blocknext block →recent activity
Analyzing
Block #91,294,661
14 transactions · 11 stateful · 2026-07-29 08:21:09 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,294,661 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3601aa45…29cb
0x34b655…2a6f
4 touches
1 conflict
0x9abd6f25…4a4e
0x34b655…2a6f
4 touches
1 conflict
0xb2195a0c…68ca
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x446e4f62…f7b6
0x34b655…2a6f
2 touches
0 conflicts
0x55cf4758…265c
0x34b655…2a6f
2 touches
0 conflicts
0x66f43740…ff14
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity