← previous blocknext block →recent activity
Analyzing
Block #91,435,362
19 transactions · 18 stateful · 2026-07-29 20:10:26 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,435,362 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w110w214w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x52e88fc2…bbcf
0x34b655…2a6f
6 touches
3 conflicts
0xe2ca9bf2…8da8
0x34b655…2a6f
6 touches
3 conflicts
0x57e610bf…fd64
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity