← previous blocknext block →recent activity
Analyzing
Block #86,957,360
56 transactions · 44 stateful · 2026-07-11 01:42:42 UTC
Parallelism
77/100
Blocked
66%
Avg conflicts / tx
1.55
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #86,957,360 · 56 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w17w010w212w214w015w118w219w024w026w129w030w131w232w333w434w535w636w737w841w143w144w245w346w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xb0446875…2b96
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa9cbb623…e644
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity