← previous blocknext block →recent activity
Analyzing
Block #91,977,240
15 transactions · 14 stateful · 2026-07-31 17:36:27 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,977,240 · 15 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
1w02w04w15w26w17w38w49w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x30179ede…a7df
0x7b9256…1fb2
8 touches
6 conflicts
0x30179ede…a7e0
0x7b9256…1fb2
8 touches
6 conflicts
0xf8528c06…8233
0x7b9256…1fb2
8 touches
6 conflicts
0xf8528c06…8230
0x7b9256…1fb2
8 touches
6 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
8 touches
6 conflicts
0xf8528c06…822f
0x7b9256…1fb2
8 touches
6 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity