← previous blocknext block →recent activity
Analyzing
Block #87,724,959
18 transactions · 18 stateful · 2026-07-14 15:16:15 UTC
Parallelism
50/100
Blocked
61%
Avg conflicts / tx
2.39
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,724,959 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9dce17a…a1a1
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x9ae859db…2d84
0x34b655…2a6f
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x28c62bca…b746
0x34b655…2a6f
16 touches
28 conflicts
0x0733be30…112f
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
36 conflicts on slot 0xc9dce17a10…8ca1a1
Audit this contract →
← previous block·next block →recent activity