← previous blocknext block →recent activity
Analyzing
Block #91,996,550
11 transactions · 10 stateful · 2026-07-31 19:13:35 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,996,550 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aac985d…4fff
0x7b9256…1fb2
8 touches
6 conflicts
0x6aac985d…4ffb
0x7b9256…1fb2
8 touches
6 conflicts
0x3ac062fc…0ba8
0x7b9256…1fb2
8 touches
6 conflicts
0x6aac985d…4ffc
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x3ac062fc…0ba9
0x7b9256…1fb2
8 touches
6 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
6 conflicts on slot 0x6aac985dbc…9e4fff
Audit this contract →
← previous block·next block →recent activity