← previous blocknext block →recent activity
Analyzing
Block #86,447,687
40 transactions · 36 stateful · 2026-07-08 16:53:58 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,447,687 · 40 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
1w02w13w24w35w46w212w214w515w016w117w218w319w022w123w229w631w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
12 touches
15 conflicts
0x2cf3ae67…af2b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x86dfe00e…d800
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
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
21 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity