← previous blocknext block →recent activity
Analyzing
Block #87,876,838
24 transactions · 21 stateful · 2026-07-15 08:12:09 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,876,838 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w17w09w110w211w013w117w218w319w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x846f2172…fd54
0x0555e3…2b9c
8 touches
6 conflicts
0x46cb45de…a566
0x188d58…ea8e
8 touches
6 conflicts
0x46cb45de…a567
0x188d58…ea8e
8 touches
6 conflicts
0xb439fb13…fa25
0xd32edf…ff58
7 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x55aacff5…b000
0x34b655…2a6f
4 touches
1 conflict
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: Wrapped BTC (WBTC)
6 conflicts on slot 0x846f21722e…fdfd54
Audit this contract →
← previous block·next block →recent activity