← previous blocknext block →recent activity
Analyzing
Block #87,708,061
47 transactions · 42 stateful · 2026-07-14 13:23:03 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
2.72
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,708,061 · 47 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w111w012w113w214w315w416w517w618w719w820w921w1022w1123w1224w1325w1429w130w233w337w238w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0x5b145de0…367c
0xc8689a…ee79
22 touches
55 conflicts
0x4560e5a8…b741
0x34b655…2a6f
22 touches
55 conflicts
0x67905f6e…02a1
0x34b655…2a6f
22 touches
55 conflicts
0x7525206c…fbd5
0x34b655…2a6f
22 touches
55 conflicts
0x7837c02d…0965
0x34b655…2a6f
22 touches
55 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
22 touches
55 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
22 touches
55 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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity