← previous blocknext block →recent activity
Analyzing
Block #87,726,195
13 transactions · 12 stateful · 2026-07-14 15:24:31 UTC
Parallelism
39/100
Blocked
58%
Avg conflicts / tx
2.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,726,195 · 13 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9dce17a…a1a1
0x34b655…2a6f
14 touches
21 conflicts
0x805d08cf…3cfc
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x67905f6e…02a1
0x34b655…2a6f
12 touches
15 conflicts
0x3726966a…669d
0x34b655…2a6f
12 touches
15 conflicts
0x5dccc158…65de
0x34b655…2a6f
12 touches
15 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
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
21 conflicts on slot 0xc9dce17a10…8ca1a1
Audit this contract →
← previous block·next block →recent activity