← previous blocknext block →recent activity
Analyzing
Block #87,716,508
25 transactions · 23 stateful · 2026-07-14 14:19:42 UTC
Parallelism
56/100
Blocked
61%
Avg conflicts / tx
2.64
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,716,508 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w410w511w612w719w820w923w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7525206c…fbd5
0x34b655…2a6f
22 touches
55 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
18 touches
36 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd7fd3b1f…f930
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
55 conflicts on slot 0x7525206cf5…dcfbd5
Audit this contract →
← previous block·next block →recent activity