← previous blocknext block →recent activity
Analyzing
Block #91,903,761
20 transactions · 18 stateful · 2026-07-31 11:26:52 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,903,761 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w38w412w514w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x809f2ba8…89d3
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xe112de0f…add2
0x34b655…2a6f
6 touches
3 conflicts
0x2029b74e…c206
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity