← previous blocknext block →recent activity
Analyzing
Block #91,132,496
8 transactions · 8 stateful · 2026-07-28 18:44:30 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,132,496 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c0627bd…f5c4
0x34b655…2a6f
4 touches
1 conflict
0x4c0627bd…f5c3
0x34b655…2a6f
4 touches
1 conflict
0xe1b6b3c8…6676
0x34b655…2a6f
4 touches
1 conflict
0x02fc525e…1899
0x34b655…2a6f
2 touches
0 conflicts
0x2d966132…b875
0x34b655…2a6f
2 touches
0 conflicts
0x2d9c72fd…04a1
0x34b655…2a6f
2 touches
0 conflicts
0x5060cdde…445d
0x34b655…2a6f
2 touches
0 conflicts
0x5c2199dc…c43d
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 0x4c0627bdf9…4ef5c4
Audit this contract →
← previous block·next block →recent activity