← previous blocknext block →recent activity
Analyzing
Block #87,731,804
61 transactions · 41 stateful · 2026-07-14 16:02:03 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
2.39
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,731,804 · 61 txs across 21 waves · depth 21
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
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w020w021w130w031w232w333w444w1345w1447w449w150w255w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xc4de6652…13f4
0x34b655…2a6f
22 touches
55 conflicts
0x3726966a…669d
0x34b655…2a6f
16 touches
28 conflicts
0x44beb9ca…2366
0x34b655…2a6f
16 touches
28 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
16 touches
28 conflicts
0x67905f6e…02a1
0x34b655…2a6f
16 touches
28 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
16 touches
28 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity