← previous blocknext block →recent activity
Analyzing
Block #85,679,751
9 transactions · 7 stateful · 2026-07-05 03:29:12 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,679,751 · 9 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
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedf4636f…b2a2
0x34b655…2a6f
6 touches
3 conflicts
0x8656a13f…f95e
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xc8373a2a…0804
0x34b655…2a6f
4 touches
1 conflict
0xb4aa41e0…f123
0x34b655…2a6f
3 touches
1 conflict
0x5a3e3430…7e44
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 0xedf4636f60…72b2a2
Audit this contract →
← previous block·next block →recent activity