← previous blocknext block →recent activity
Analyzing
Block #87,690,426
49 transactions · 36 stateful · 2026-07-14 11:24:53 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.57
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,690,426 · 49 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
2w04w15w06w07w111w012w121w022w123w224w325w426w527w628w729w830w934w735w1039w241w1243w144w247w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0x0f068b13…fb19
0x34b655…2a6f
8 touches
6 conflicts
0x2fdfa032…139c
0x34b655…2a6f
8 touches
6 conflicts
0xc2186704…5cc3
0x34b655…2a6f
8 touches
6 conflicts
0xdbb43016…7cc4
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x03fb27fd…0c06
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity