← previous blocknext block →recent activity
Analyzing
Block #85,176,543
14 transactions · 14 stateful · 2026-07-02 19:38:14 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,176,543 · 14 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
2w05w17w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa5b76b…60db
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x8c6bdd36…efa1
0x34b655…2a6f
4 touches
1 conflict
0xb9bc1dfc…6bfb
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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
1 conflict on slot 0x0aa5b76bf8…b060db
Audit this contract →
← previous block·next block →recent activity