← previous blocknext block →recent activity
Analyzing
Block #85,212,341
10 transactions · 9 stateful · 2026-07-02 23:36:37 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,212,341 · 10 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
2w04w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1aad6e5…9135
0x34b655…2a6f
6 touches
3 conflicts
0x3afc31a6…3b44
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x116152da…4dd2
0x34b655…2a6f
4 touches
1 conflict
0x00c45c58…7df2
0x34b655…2a6f
2 touches
0 conflicts
0x03a55247…abfe
0x34b655…2a6f
2 touches
0 conflicts
0x1b4b5036…a600
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 0xc1aad6e5d4…f89135
Audit this contract →
← previous block·next block →recent activity