← previous blocknext block →recent activity
Analyzing
Block #85,135,592
18 transactions · 15 stateful · 2026-07-02 15:05:30 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,135,592 · 18 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
4w05w16w28w110w011w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb04d17a0…10e8
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7c63ea28…e8af
0x34b655…2a6f
5 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x353d9082…4d53
0x34b655…2a6f
4 touches
1 conflict
0x396b97d6…3981
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xb04d17a0fe…4810e8
Audit this contract →
← previous block·next block →recent activity