← previous blocknext block →recent activity
Analyzing
Block #85,353,064
10 transactions · 9 stateful · 2026-07-03 15:14:03 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,353,064 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10d9dbcb…9fdb
0x34b655…2a6f
4 touches
1 conflict
0x6eac5a5d…1730
0x34b655…2a6f
4 touches
1 conflict
0xa29182a1…c12c
0x34b655…2a6f
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x26b3d62a…1dc8
0x34b655…2a6f
2 touches
0 conflicts
0x319506e8…121a
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
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 0x10d9dbcba8…039fdb
Audit this contract →
← previous block·next block →recent activity