← previous blocknext block →recent activity
Analyzing
Block #87,717,761
21 transactions · 20 stateful · 2026-07-14 14:28:07 UTC
Parallelism
52/100
Blocked
60%
Avg conflicts / tx
2.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,717,761 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w710w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7525206c…fbd5
0x34b655…2a6f
18 touches
36 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x13510de3…1c68
0x34b655…2a6f
16 touches
28 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x6d85c11e…9c54
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 0x7525206cf5…dcfbd5
Audit this contract →
← previous block·next block →recent activity