← previous blocknext block →recent activity
Analyzing
Block #87,759,127
27 transactions · 26 stateful · 2026-07-14 19:04:47 UTC
Parallelism
59/100
Blocked
54%
Avg conflicts / tx
1.7
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,759,127 · 27 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
1w02w15w06w17w28w39w410w511w612w725w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x20ff72d4…5971
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0xa80684c9…3948
0x34b655…2a6f
10 touches
10 conflicts
0xca18c58e…cede
0x34b655…2a6f
10 touches
10 conflicts
0x9001f549…089d
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity