← previous blocknext block →recent activity
Analyzing
Block #87,354,946
43 transactions · 35 stateful · 2026-07-12 22:00:48 UTC
Parallelism
63/100
Blocked
71%
Avg conflicts / tx
2.88
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,354,946 · 43 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w39w416w017w118w219w320w421w522w623w724w825w931w432w133w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0xf81d0d0f…cf78
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x3413a430…234a
0x34b655…2a6f
12 touches
15 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
11 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity