← previous blocknext block →recent activity
Analyzing
Block #85,352,134
22 transactions · 21 stateful · 2026-07-03 15:07:51 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,352,134 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w311w113w414w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5dbfacf…c5ec
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x37534430…c68b
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x4b628349…f327
0x34b655…2a6f
4 touches
1 conflict
0x319506e8…121a
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
1 conflict on slot 0xd5dbfacf04…49c5ec
Audit this contract →
← previous block·next block →recent activity