← previous blocknext block →recent activity
Analyzing
Block #91,250,168
36 transactions · 35 stateful · 2026-07-29 04:36:30 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,250,168 · 36 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w38w09w010w112w013w115w116w217w322w123w224w325w427w330w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x03aa8b26…118a
0x34b655…2a6f
8 touches
6 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x7be3246e…f89f
0x34b655…2a6f
8 touches
6 conflicts
0x4cfa19ab…6413
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…004c
0x80c745…7210
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity