← previous blocknext block →recent activity
Analyzing
Block #87,518,169
19 transactions · 19 stateful · 2026-07-13 16:12:35 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,518,169 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w38w09w110w311w412w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
10 touches
10 conflicts
0x5ad8135f…d8e6
0x34b655…2a6f
8 touches
6 conflicts
0x3817764d…242b
0x34b655…2a6f
8 touches
6 conflicts
0xc799e56d…45aa
0x34b655…2a6f
6 touches
3 conflicts
0x0406a8bb…39a9
0x34b655…2a6f
6 touches
3 conflicts
0x1ffbc5c9…461f
0x34b655…2a6f
6 touches
3 conflicts
0x3f3d0666…5614
0x34b655…2a6f
6 touches
3 conflicts
0xb2b669ab…96b2
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
10 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity