← previous blocknext block →recent activity
Analyzing
Block #91,959,115
21 transactions · 20 stateful · 2026-07-31 16:05:18 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,959,115 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w110w011w112w213w214w215w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec4a54ae…7968
0x7b9256…1fb2
6 touches
3 conflicts
0xec4a54ae…7967
0x7b9256…1fb2
6 touches
3 conflicts
0xec4a54ae…796b
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x968dca28…a34b
0x7b9256…1fb2
6 touches
3 conflicts
0x968dca28…a34c
0x7b9256…1fb2
6 touches
3 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: 0x7b9256fd…e21fb2
3 conflicts on slot 0xec4a54ae41…9f7968
Audit this contract →
← previous block·next block →recent activity