← previous blocknext block →recent activity
Analyzing
Block #91,188,885
13 transactions · 10 stateful · 2026-07-28 23:28:10 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,188,885 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0xb5f244d5…f550
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity