← previous blocknext block →recent activity
Analyzing
Block #85,213,662
11 transactions · 9 stateful · 2026-07-02 23:45:25 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,213,662 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xceb535f3…19cf
0x34b655…2a6f
6 touches
3 conflicts
0xb577a4a7…a670
0x34b655…2a6f
4 touches
1 conflict
0xc9ce5af1…3c1c
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5271f1a1…7cd5
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x1af777a9…b403
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
3 conflicts on slot 0xceb535f356…6319cf
Audit this contract →
← previous block·next block →recent activity