← previous blocknext block →recent activity
Analyzing
Block #90,678,618
10 transactions · 10 stateful · 2026-07-27 04:40:08 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,678,618 · 10 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
2w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0xa15e2d91…025a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1b9c85ed…74cb
0x34b655…2a6f
2 touches
0 conflicts
0x52a2ba74…f2f6
0x34b655…2a6f
2 touches
0 conflicts
0x52a2ba74…f2f7
0x34b655…2a6f
2 touches
0 conflicts
0x6641a47b…d683
0x34b655…2a6f
2 touches
0 conflicts
0x6925548b…81cb
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 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity