← previous blocknext block →recent activity
Analyzing
Block #87,704,764
49 transactions · 39 stateful · 2026-07-14 13:00:58 UTC
Parallelism
67/100
Blocked
69%
Avg conflicts / tx
2.67
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,704,764 · 49 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
1w02w13w05w16w29w010w016w117w018w119w220w321w422w523w624w725w826w927w1028w1129w1230w1331w1435w243w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
18 touches
36 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
18 touches
36 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
16 touches
28 conflicts
0x7837c02d…0965
0x34b655…2a6f
16 touches
28 conflicts
0x4560e5a8…b741
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 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