← previous blocknext block →recent activity
Analyzing
Block #85,101,701
10 transactions · 9 stateful · 2026-07-02 11:18:35 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,101,701 · 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1e4de02…07e9
0x34b655…2a6f
4 touches
1 conflict
0x7fd302db…0c73
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x370597f0…d806
0x1efe02…37d6
2 touches
0 conflicts
0x390e91e0…b090
0x1efe02…37d6
2 touches
0 conflicts
0x4a41bd2e…1bfc
0x1efe02…37d6
2 touches
0 conflicts
0x661f4e6b…39a5
0x1efe02…37d6
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 0xd1e4de026f…2607e9
Audit this contract →
← previous block·next block →recent activity