← previous blocknext block →recent activity
Analyzing
Block #86,663,475
19 transactions · 18 stateful · 2026-07-09 16:59:00 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
0.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,663,475 · 19 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
1w04w05w16w27w39w110w411w112w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0x32654609…aac8
0x34b655…2a6f
4 touches
1 conflict
0x3bc7cb73…e46d
0x34b655…2a6f
4 touches
1 conflict
0x4c8db472…d62e
0x34b655…2a6f
4 touches
1 conflict
0x60c7217a…8c94
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity