← previous blocknext block →recent activity
Analyzing
Block #91,810,191
10 transactions · 9 stateful · 2026-07-31 03:36:03 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,810,191 · 10 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
2w03w14w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fd12b6c…02cc
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x3932086f…b68b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x1334adaf…1ee6
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
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
10 conflicts on slot 0x2fd12b6c73…8702cc
Audit this contract →
← previous block·next block →recent activity