← previous blocknext block →recent activity
Analyzing
Block #91,111,242
21 transactions · 20 stateful · 2026-07-28 16:57:35 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,111,242 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w19w010w111w112w217w318w419w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa300902c…009e
0x34b655…2a6f
6 touches
3 conflicts
0x103f63b2…ff11
0x34b655…2a6f
4 touches
1 conflict
0x2bad40ae…0522
0x34b655…2a6f
4 touches
1 conflict
0x41377979…0a18
0x34b655…2a6f
4 touches
1 conflict
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0x5754ed4f…e095
0x34b655…2a6f
4 touches
1 conflict
0x5b36ef9c…3370
0x34b655…2a6f
4 touches
1 conflict
0x65487580…b5eb
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
3 conflicts on slot 0xa300902c66…f8009e
Audit this contract →
← previous block·next block →recent activity