← previous blocknext block →recent activity
Analyzing
Block #87,731,780
75 transactions · 51 stateful · 2026-07-14 16:01:53 UTC
Parallelism
73/100
Blocked
65%
Avg conflicts / tx
3.16
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,731,780 · 75 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
7w010w113w214w320w021w137w038w139w240w341w442w557w659w1361w165w466w573w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
38 touches
171 conflicts
0xc4de6652…13f4
0x34b655…2a6f
16 touches
28 conflicts
0x3726966a…669d
0x34b655…2a6f
14 touches
21 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
14 touches
21 conflicts
0x67905f6e…02a1
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 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
171 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity