← previous blocknext block →recent activity
Analyzing
Block #90,789,828
17 transactions · 16 stateful · 2026-07-27 13:59:37 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,789,828 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w19w110w212w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x007892de…5752
0x34b655…2a6f
8 touches
6 conflicts
0xde945aa8…1ad5
0xa6afd3…d132
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x561ad161…c172
0xa6afd3…d132
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0xa629d950…36f6
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 0x007892de1e…635752
Audit this contract →
← previous block·next block →recent activity