← previous blocknext block →recent activity
Analyzing
Block #87,706,479
30 transactions · 28 stateful · 2026-07-14 13:12:28 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
2.6
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,706,479 · 30 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
5w06w17w28w39w410w511w612w713w814w919w124w1025w1128w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
22 touches
55 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
18 touches
36 conflicts
0x7837c02d…0965
0x34b655…2a6f
18 touches
36 conflicts
0x67905f6e…02a1
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
18 touches
36 conflicts
0x4560e5a8…b741
0x34b655…2a6f
18 touches
36 conflicts
0x3def7c2a…59e0
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
55 conflicts on slot 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity