← previous blocknext block →recent activity
Analyzing
Block #87,748,932
61 transactions · 54 stateful · 2026-07-14 17:56:38 UTC
Parallelism
72/100
Blocked
78%
Avg conflicts / tx
2.84
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,748,932 · 61 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w112w213w314w015w116w217w319w020w121w222w323w449w153w254w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x00000000…0001
0xc1ff9f…b0fc
20 touches
45 conflicts
0x9a2de05d…3e6b
0x34b655…2a6f
12 touches
15 conflicts
0x428b6e5b…8909
0x34b655…2a6f
10 touches
10 conflicts
0x58620f29…db5a
0x34b655…2a6f
8 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x64275949…d698
0x34b655…2a6f
8 touches
6 conflicts
0x70f537e8…399b
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity