← previous blocknext block →recent activity
Analyzing
Block #85,363,398
25 transactions · 23 stateful · 2026-07-03 16:22:53 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,363,398 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w17w08w19w110w212w215w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f24a374…6bc3
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdba422af…42ec
0x34b655…2a6f
6 touches
3 conflicts
0x01414ad2…98ec
0x34b655…2a6f
4 touches
1 conflict
0x080ec687…da80
0x34b655…2a6f
4 touches
1 conflict
0x13a5a8fa…2b18
0x34b655…2a6f
4 touches
1 conflict
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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
6 conflicts on slot 0x3f24a37442…3c6bc3
Audit this contract →
← previous block·next block →recent activity