← previous blocknext block →recent activity
Analyzing
Block #91,019,826
14 transactions · 13 stateful · 2026-07-28 09:17:35 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,019,826 · 14 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
3w04w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe37a080…291a
0x34b655…2a6f
6 touches
3 conflicts
0xd35fa247…3e18
0x34b655…2a6f
4 touches
1 conflict
0xff29965b…b918
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1ebb35bb…ef2a
0x34b655…2a6f
4 touches
1 conflict
0x322fb0e8…962d
0x34b655…2a6f
4 touches
1 conflict
0x59052228…add7
0x34b655…2a6f
4 touches
1 conflict
0x6483a537…b63e
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xfe37a08059…ff291a
Audit this contract →
← previous block·next block →recent activity