← previous blocknext block →recent activity
Analyzing
Block #91,008,716
12 transactions · 12 stateful · 2026-07-28 08:21:34 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,008,716 · 12 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
2w03w14w25w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6034d48f…03c7
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
0x12cf8e3a…699d
0x7b9256…1fb2
8 touches
6 conflicts
0x12cf8e3a…699e
0x7b9256…1fb2
8 touches
6 conflicts
0x12cf8e3a…69a1
0x7b9256…1fb2
8 touches
6 conflicts
0x6034d48f…03c6
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 0x6034d48fe8…b903c7
Audit this contract →
← previous block·next block →recent activity