← previous blocknext block →recent activity
Analyzing
Block #90,510,502
9 transactions · 9 stateful · 2026-07-26 14:34:26 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,510,502 · 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
3w04w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0xabd0bcfc…64e2
0x34b655…2a6f
4 touches
1 conflict
0x1966c07e…fd4b
0x34b655…2a6f
4 touches
1 conflict
0x2894b5dd…5c2e
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
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 0x9b2d3bee9d…d68eec
Audit this contract →
← previous block·next block →recent activity