← previous blocknext block →recent activity
Analyzing
Block #91,124,847
7 transactions · 5 stateful · 2026-07-28 18:06:02 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,124,847 · 7 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0xbeed7137…b58e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x04c1c529…0ee1
0x34b655…2a6f
2 touches
0 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
2 touches
0 conflicts
0x27dca182…8ebe
0x34b655…2a6f
2 touches
0 conflicts
0x36b7c966…ba5c
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 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity