← previous blocknext block →recent activity
Analyzing
Block #85,198,231
10 transactions · 9 stateful · 2026-07-02 22:02:41 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,198,231 · 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
1w05w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ba4db2b…2f04
0x34b655…2a6f
4 touches
1 conflict
0xb04d17a0…10e8
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0xb44564d6…bb43
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x379bef0d…1d85
0x34b655…2a6f
2 touches
0 conflicts
0x3d352bc9…4895
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
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 0x5ba4db2bd6…572f04
Audit this contract →
← previous block·next block →recent activity