← previous blocknext block →recent activity
Analyzing
Block #91,025,657
19 transactions · 17 stateful · 2026-07-28 09:46:56 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,025,657 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w08w19w210w313w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c0e32fc…a6ca
0x34b655…2a6f
8 touches
6 conflicts
0x81f842e8…939f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x529e8f13…967a
0x34b655…2a6f
7 touches
6 conflicts
0x6e6a8155…9636
0x34b655…2a6f
6 touches
3 conflicts
0x7648af81…2af3
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x6c0e32fc91…09a6ca
Audit this contract →
← previous block·next block →recent activity