← previous blocknext block →recent activity
Analyzing
Block #90,804,691
9 transactions · 8 stateful · 2026-07-27 15:14:23 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,804,691 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf4ef432…d64c
0x34b655…2a6f
4 touches
1 conflict
0x1f6f8ff8…a5d5
0x34b655…2a6f
4 touches
1 conflict
0x1f6f8ff8…a5d4
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x8eb01335…f3fd
0x34b655…2a6f
4 touches
1 conflict
0x4ff85046…e2f5
0x34b655…2a6f
3 touches
1 conflict
0x4bd1d7fb…b907
0x34b655…2a6f
2 touches
0 conflicts
0x5f188956…44a6
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 0xcf4ef432e5…e5d64c
Audit this contract →
← previous block·next block →recent activity