← previous blocknext block →recent activity
Analyzing
Block #87,489,882
38 transactions · 33 stateful · 2026-07-13 13:03:11 UTC
Parallelism
71/100
Blocked
73%
Avg conflicts / tx
2.29
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,489,882 · 38 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
1w04w05w17w19w010w111w012w113w214w316w117w218w319w420w521w623w724w827w328w729w830w231w332w433w536w937w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xc3688185…9b36
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0001
0xc1ff9f…b0fc
10 touches
10 conflicts
0xa020506f…7c60
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x4c04ce68…d007
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
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