← previous blocknext block →recent activity
Analyzing
Block #87,698,418
52 transactions · 43 stateful · 2026-07-14 12:18:17 UTC
Parallelism
67/100
Blocked
77%
Avg conflicts / tx
3
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,698,418 · 52 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w17w210w311w012w113w215w016w117w219w320w435w142w343w245w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0x00000000…0001
0xc1ff9f…b0fc
10 touches
10 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
10 touches
10 conflicts
0xca18c58e…cede
0x34b655…2a6f
8 touches
6 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity