← previous blocknext block →recent activity
Analyzing
Block #85,371,702
21 transactions · 18 stateful · 2026-07-03 17:18:15 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,371,702 · 21 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
2w03w16w07w19w010w111w212w014w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f34fd08…aeb3
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x57bb625a…286d
0x34b655…2a6f
6 touches
3 conflicts
0x342a12bc…c045
0x34b655…2a6f
4 touches
1 conflict
0x8eef8244…5c91
0x34b655…2a6f
4 touches
1 conflict
0xcd370c0d…3257
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
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 0x5f34fd08e4…a5aeb3
Audit this contract →
← previous block·next block →recent activity