← previous blocknext block →recent activity
Analyzing
Block #85,283,140
13 transactions · 13 stateful · 2026-07-03 07:28:15 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,283,140 · 13 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
1w02w07w18w29w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e2eda1…396f
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0xb79e603a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xbf140d9d…4923
0x34b655…2a6f
4 touches
1 conflict
0xc57747c0…99d1
0x34b655…2a6f
4 touches
1 conflict
0xdd3e925c…23ac
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
3 conflicts on slot 0x43e2eda154…aa396f
Audit this contract →
← previous block·next block →recent activity