← previous blocknext block →recent activity
Analyzing
Block #85,138,474
20 transactions · 17 stateful · 2026-07-02 15:24:44 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,138,474 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w08w19w110w111w013w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e2eda1…396f
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x946df593…4a0c
0x34b655…2a6f
6 touches
3 conflicts
0x12c6929d…e7db
0x34b655…2a6f
4 touches
1 conflict
0x5ab1d302…9100
0x34b655…2a6f
4 touches
1 conflict
0x644919d7…9727
0x34b655…2a6f
4 touches
1 conflict
0xab3a7dc6…0ed8
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
6 conflicts on slot 0x43e2eda154…aa396f
Audit this contract →
← previous block·next block →recent activity