← previous blocknext block →recent activity
Analyzing
Block #87,709,130
53 transactions · 38 stateful · 2026-07-14 13:30:12 UTC
Parallelism
74/100
Blocked
68%
Avg conflicts / tx
1.92
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,709,130 · 53 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w210w411w512w014w124w025w126w227w328w429w530w631w732w833w934w1035w1140w644w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf565ea1f…4245
0x34b655…2a6f
10 touches
10 conflicts
0x7837c02d…0965
0x34b655…2a6f
8 touches
6 conflicts
0x4560e5a8…b741
0x34b655…2a6f
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity