← previous blocknext block →recent activity
Analyzing
Block #90,616,148
15 transactions · 15 stateful · 2026-07-26 23:25:52 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,616,148 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00dcbc22…8053
0x34b655…2a6f
4 touches
1 conflict
0x97e2bfcd…fb19
0x34b655…2a6f
4 touches
1 conflict
0xbeda8507…4e81
0x34b655…2a6f
4 touches
1 conflict
0xdb455dbf…e30c
0x34b655…2a6f
4 touches
1 conflict
0x3eede796…d745
0x34b655…2a6f
2 touches
0 conflicts
0x6adf6a33…2ffb
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity