← previous blocknext block →recent activity
Analyzing
Block #87,792,276
62 transactions · 48 stateful · 2026-07-14 22:46:35 UTC
Parallelism
68/100
Blocked
71%
Avg conflicts / tx
2.84
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,792,276 · 62 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
1w02w13w06w17w210w311w412w020w022w123w224w325w426w527w647w548w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
32 touches
120 conflicts
0x00000000…0001
0xc1ff9f…b0fc
14 touches
21 conflicts
0x0b42fe4a…f5c4
0x34b655…2a6f
10 touches
10 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
10 touches
10 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
10 touches
10 conflicts
0x6e88d93a…6c59
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x04a566e1…26f3
0x34b655…2a6f
10 touches
10 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
120 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity