← previous blocknext block →recent activity
Analyzing
Block #90,819,878
21 transactions · 21 stateful · 2026-07-27 16:30:53 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,819,878 · 21 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
4w05w16w29w010w111w312w415w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a2c83a3…a29a
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xac799015…5ab0
0x34b655…2a6f
4 touches
1 conflict
0xc2882006…936f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xce7d5758…0a52
0x34b655…2a6f
4 touches
1 conflict
0xe4fa0d96…f772
0x34b655…2a6f
4 touches
1 conflict
0xf18906a6…d2e3
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 0x7a2c83a30a…f3a29a
Audit this contract →
← previous block·next block →recent activity