← previous blocknext block →recent activity
Analyzing
Block #87,624,377
35 transactions · 31 stateful · 2026-07-14 04:03:29 UTC
Parallelism
57/100
Blocked
61%
Avg conflicts / tx
2.34
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,624,377 · 35 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w07w110w011w112w213w314w415w516w617w718w819w920w1021w1127w133w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x08330b36…ae29
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x38b697c2…c3f3
0x34b655…2a6f
8 touches
6 conflicts
0x4560e5a8…b741
0x34b655…2a6f
8 touches
6 conflicts
0x4f4a7ac3…021c
0x34b655…2a6f
8 touches
6 conflicts
0x9599eb41…b5d6
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity