← previous blocknext block →recent activity
Analyzing
Block #90,790,835
15 transactions · 15 stateful · 2026-07-27 14:04:41 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,790,835 · 15 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
1w03w04w15w27w18w29w310w412w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b89cd8…5092
0x34b655…2a6f
8 touches
6 conflicts
0x3910ea4e…c5cc
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xda27c764…7fab
0x34b655…2a6f
6 touches
3 conflicts
0x3b247873…675a
0x34b655…2a6f
5 touches
3 conflicts
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0x6a1604d1…3e8a
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
6 conflicts on slot 0x35b89cd80c…f05092
Audit this contract →
← previous block·next block →recent activity