← previous blocknext block →recent activity
Analyzing
Block #87,419,562
22 transactions · 20 stateful · 2026-07-13 05:13:02 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,419,562 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w28w39w410w511w612w716w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
10 touches
10 conflicts
0x7741f0f6…b99c
0x34b655…2a6f
10 touches
10 conflicts
0x458c8f89…d23c
0x34b655…2a6f
8 touches
6 conflicts
0x0eac7709…66c3
0x34b655…2a6f
8 touches
6 conflicts
0x0f6aef87…8137
0x34b655…2a6f
8 touches
6 conflicts
0x37d710c8…45c1
0x34b655…2a6f
8 touches
6 conflicts
0xb5f244d5…f550
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity