← previous blocknext block →recent activity
Analyzing
Block #91,984,031
19 transactions · 17 stateful · 2026-07-31 18:10:36 UTC
Parallelism
84/100
Blocked
18%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,984,031 · 19 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
1w05w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7e2686d…4438
0x7b9256…1fb2
6 touches
3 conflicts
0xe7e2686d…4439
0x7b9256…1fb2
6 touches
3 conflicts
0xe7e2686d…443c
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
0xa3d54bdd…a448
0x7b9256…1fb2
6 touches
3 conflicts
0xa3d54bdd…a449
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 0xe7e2686d36…394438
Audit this contract →
← previous block·next block →recent activity