← previous blocknext block →recent activity
Analyzing
Block #90,289,729
14 transactions · 14 stateful · 2026-07-25 19:50:05 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,289,729 · 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
5w06w07w18w29w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6939e474…4256
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x96dd83e6…a507
0x34b655…2a6f
4 touches
1 conflict
0xac62ede4…57c0
0x34b655…2a6f
4 touches
1 conflict
0xac62ede4…57c1
0x34b655…2a6f
4 touches
1 conflict
0xc39338bf…d0e7
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 0x6939e474b1…154256
Audit this contract →
← previous block·next block →recent activity