← previous blocknext block →recent activity
Analyzing
Block #87,787,646
20 transactions · 18 stateful · 2026-07-14 22:15:37 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,787,646 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w312w013w314w416w518w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
8 touches
6 conflicts
0xbd6e61f7…3ede
0x34b655…2a6f
8 touches
6 conflicts
0x634daab4…dd5e
0x34b655…2a6f
6 touches
3 conflicts
0x80467952…c46f
0x34b655…2a6f
6 touches
3 conflicts
0x3fde350e…8d43
0x34b655…2a6f
6 touches
3 conflicts
0xcf430d5c…48ef
0x34b655…2a6f
6 touches
3 conflicts
0x587911c7…9e01
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity