← previous blocknext block →recent activity
Analyzing
Block #87,504,490
25 transactions · 22 stateful · 2026-07-13 14:40:58 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,504,490 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w17w28w39w410w514w615w318w420w523w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02ad5c19…f593
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xe5a38e46…a68c
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
6 touches
3 conflicts
0x0639c99c…66a2
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x4943ce42…cab3
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x02ad5c1905…1df593
Audit this contract →
← previous block·next block →recent activity