← previous blocknext block →recent activity
Analyzing
Block #87,624,662
34 transactions · 30 stateful · 2026-07-14 04:05:23 UTC
Parallelism
59/100
Blocked
70%
Avg conflicts / tx
2.79
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,624,662 · 34 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w07w110w011w112w213w314w415w516w618w419w720w822w224w1025w326w430w1031w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
12 touches
15 conflicts
0x24f6d4ca…c33b
0x34b655…2a6f
12 touches
15 conflicts
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x08330b36…ae29
0x34b655…2a6f
12 touches
15 conflicts
0x7f54c47a…ffaa
0x34b655…2a6f
10 touches
10 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
10 touches
10 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity