← previous blocknext block →recent activity
Analyzing
Block #87,710,040
44 transactions · 37 stateful · 2026-07-14 13:36:18 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.59
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,710,040 · 44 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w012w114w217w118w219w320w421w522w623w724w826w231w334w1039w1140w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x23961159…1e02
0x34b655…2a6f
12 touches
15 conflicts
0x015c28a0…37da
0x34b655…2a6f
12 touches
15 conflicts
0x072137cd…a3b8
0x34b655…2a6f
12 touches
15 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
12 touches
15 conflicts
0x3a041575…77bb
0x34b655…2a6f
12 touches
15 conflicts
0x5c591136…d322
0x34b655…2a6f
12 touches
15 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