← previous blocknext block →recent activity
Analyzing
Block #91,108,599
19 transactions · 18 stateful · 2026-07-28 16:44:18 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,108,599 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w110w011w112w215w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0xbfd744bf…c9dd
0x7b9256…1fb2
6 touches
3 conflicts
0xbfd744bf…c9de
0x7b9256…1fb2
6 touches
3 conflicts
0xc561db58…139a
0x7b9256…1fb2
6 touches
3 conflicts
0xc561db58…139b
0x7b9256…1fb2
6 touches
3 conflicts
0xc561db58…139e
0x7b9256…1fb2
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
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 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity