← previous blocknext block →recent activity
Analyzing
Block #91,764,310
34 transactions · 26 stateful · 2026-07-30 23:45:14 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,764,310 · 34 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
5w07w18w09w010w114w116w118w019w220w325w426w331w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a2c83a3…a29a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x6a46e23f…d28d
0x34b655…2a6f
6 touches
3 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b77
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
6 conflicts on slot 0x7a2c83a30a…f3a29a
Audit this contract →
← previous block·next block →recent activity