← previous blocknext block →recent activity
Analyzing
Block #90,455,592
10 transactions · 9 stateful · 2026-07-26 09:58:10 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,455,592 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w27w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54391ab3…c33b
0x34b655…2a6f
6 touches
3 conflicts
0x1a5d321d…a474
0x34b655…2a6f
6 touches
3 conflicts
0x3e1b21c6…b1e4
0x34b655…2a6f
4 touches
1 conflict
0x6767539b…f211
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x808129fc…f97d
0x34b655…2a6f
4 touches
1 conflict
0x972273bf…d60c
0x34b655…2a6f
4 touches
1 conflict
0x9a73834c…0f51
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
3 conflicts on slot 0x54391ab3c2…0dc33b
Audit this contract →
← previous block·next block →recent activity