← previous blocknext block →recent activity
Analyzing
Block #87,750,266
23 transactions · 22 stateful · 2026-07-14 18:05:33 UTC
Parallelism
39/100
Blocked
73%
Avg conflicts / tx
3.57
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,750,266 · 23 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w39w410w511w613w714w815w816w919w1020w1121w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x587911c7…9e01
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x5d7f309d…5145
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x63c900f4…2600
0x34b655…2a6f
10 touches
10 conflicts
0xad0c7701…1d83
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
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 0x587911c74f…109e01
Audit this contract →
← previous block·next block →recent activity