← previous blocknext block →recent activity
Analyzing
Block #91,140,716
20 transactions · 16 stateful · 2026-07-28 19:25:52 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,140,716 · 20 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
1w02w13w24w38w49w010w111w012w213w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71bbf601…5874
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xbc66586e…20fe
0x34b655…2a6f
10 touches
10 conflicts
0xab4f5382…087b
0xd32edf…ff58
9 touches
10 conflicts
0xa779293b…5e59
0x34b655…2a6f
6 touches
3 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
4 touches
1 conflict
0x98b8e5ef…bda4
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
15 conflicts on slot 0x71bbf601cd…6a5874
Audit this contract →
← previous block·next block →recent activity