← previous blocknext block →recent activity
Analyzing
Block #90,626,889
15 transactions · 14 stateful · 2026-07-27 00:19:54 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,626,889 · 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
2w03w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x3eede796…d745
0x34b655…2a6f
4 touches
1 conflict
0xb30b036e…c0af
0x34b655…2a6f
4 touches
1 conflict
0xc6b604e6…5152
0x34b655…2a6f
4 touches
1 conflict
0x53699236…fede
0x34b655…2a6f
4 touches
1 conflict
0x1dafc5cd…f56f
0x34b655…2a6f
2 touches
0 conflicts
0x217bd767…b79e
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
1 conflict on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity