← previous blocknext block →recent activity
Analyzing
Block #87,613,442
23 transactions · 19 stateful · 2026-07-14 02:50:22 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.78
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,613,442 · 23 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
3w04w16w07w18w211w012w015w116w317w218w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49f75237…44f4
0x34b655…2a6f
6 touches
3 conflicts
0x6280c6c6…11ac
0x34b655…2a6f
6 touches
3 conflicts
0x75b43fdd…8dc1
0x34b655…2a6f
6 touches
3 conflicts
0x7d734d5f…c6df
0x34b655…2a6f
6 touches
3 conflicts
0x91d48be7…e4e8
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity