← previous blocknext block →recent activity
Analyzing
Block #85,408,847
12 transactions · 11 stateful · 2026-07-03 21:25:33 UTC
Parallelism
75/100
Blocked
18%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,408,847 · 12 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
5w06w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96a35ba8…3d0c
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
4 touches
1 conflict
0xfb45b670…1e0a
0x34b655…2a6f
4 touches
1 conflict
0x357bc9a5…e7cb
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0xb45bb3f9…7659
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 0x96a35ba882…583d0c
Audit this contract →
← previous block·next block →recent activity