← previous blocknext block →recent activity
Analyzing
Block #86,359,004
14 transactions · 13 stateful · 2026-07-08 07:01:27 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,359,004 · 14 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
1w05w16w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xef17b8cd…9511
0x34b655…2a6f
6 touches
3 conflicts
0x4d3e58e0…a2d7
0x34b655…2a6f
5 touches
3 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
4 touches
1 conflict
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0x3904851c…9cad
0x34b655…2a6f
4 touches
1 conflict
0xc03846bb…73b3
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity