← previous blocknext block →recent activity
Analyzing
Block #87,642,741
40 transactions · 33 stateful · 2026-07-14 06:06:14 UTC
Parallelism
55/100
Blocked
73%
Avg conflicts / tx
3.4
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,642,741 · 40 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w010w111w212w313w414w515w616w717w818w920w621w726w1027w228w332w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
24 touches
66 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x4560e5a8…b741
0x34b655…2a6f
16 touches
28 conflicts
0x49f75237…44f4
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0xed59b1cd…8509
0x34b655…2a6f
16 touches
28 conflicts
0x7837c02d…0965
0x34b655…2a6f
16 touches
28 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
16 touches
28 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
66 conflicts on slot 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity