← previous blocknext block →recent activity
Analyzing
Block #85,280,948
9 transactions · 7 stateful · 2026-07-03 07:13:38 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,280,948 · 9 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2de2656d…5bbc
0x34b655…2a6f
4 touches
1 conflict
0x43e2eda1…396f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x52c63247…ce02
0x0c65a0…0852
2 touches
0 conflicts
0x86a3062f…c3f8
0x0c65a0…0852
2 touches
0 conflicts
0x14f6fe51…1c24
0x34b655…2a6f
2 touches
0 conflicts
0x225c3858…2a9b
0x34b655…2a6f
2 touches
0 conflicts
0x3750b746…5a9e
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 0x2de2656dd0…a95bbc
Audit this contract →
← previous block·next block →recent activity