← previous blocknext block →recent activity
Analyzing
Block #87,717,594
46 transactions · 33 stateful · 2026-07-14 14:27:00 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
1.83
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,717,594 · 46 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
1w04w05w112w213w017w121w022w123w224w325w326w427w528w629w730w833w935w236w1037w242w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0x7525206c…fbd5
0x34b655…2a6f
10 touches
10 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbf0e051a…10a0
0x34b655…2a6f
8 touches
6 conflicts
0x13510de3…1c68
0x34b655…2a6f
8 touches
6 conflicts
0x5bbf50c8…cb27
0x34b655…2a6f
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity