← previous blocknext block →recent activity
Analyzing
Block #85,570,516
16 transactions · 15 stateful · 2026-07-04 15:21:57 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,570,516 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9092da13…341b
0x34b655…2a6f
7 touches
6 conflicts
0xb0446875…2b96
0x34b655…2a6f
6 touches
3 conflicts
0x62341e2a…2d78
0x34b655…2a6f
6 touches
3 conflicts
0xcd4227d4…c28d
0x34b655…2a6f
6 touches
3 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity