← previous blocknext block →recent activity
Analyzing
Block #90,485,017
10 transactions · 9 stateful · 2026-07-26 12:26:14 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,485,017 · 10 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
1w02w13w24w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x037b382e…e2db
0x34b655…2a6f
2 touches
0 conflicts
0x03cf8a66…08c6
0x34b655…2a6f
2 touches
0 conflicts
0x05dabb1a…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x277e1123…149d
0x34b655…2a6f
2 touches
0 conflicts
0x2edb0a6e…06c3
0x34b655…2a6f
2 touches
0 conflicts
0x30621d87…1951
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity