← previous blocknext block →recent activity
Analyzing
Block #91,410,250
34 transactions · 27 stateful · 2026-07-29 18:03:10 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,410,250 · 34 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
1w04w16w27w38w013w114w215w318w019w120w223w025w026w229w130w231w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x17892f2d…7dea
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
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: 0x48cba278…e2b48b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity