← previous blocknext block →recent activity
Analyzing
Block #87,708,000
56 transactions · 43 stateful · 2026-07-14 13:22:38 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
2.63
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,708,000 · 56 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w28w314w015w121w022w123w224w325w426w527w628w729w830w942w443w548w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
12 touches
15 conflicts
0x7525206c…fbd5
0x34b655…2a6f
12 touches
15 conflicts
0x1803586e…d149
0xa6afd3…d132
12 touches
15 conflicts
0x7837c02d…0965
0x34b655…2a6f
12 touches
15 conflicts
0x4560e5a8…b741
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity