← previous blocknext block →recent activity
Analyzing
Block #87,717,227
19 transactions · 19 stateful · 2026-07-14 14:24:33 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,717,227 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w09w113w115w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9dce17a…a1a1
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x67905f6e…02a1
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x98834cc0…6c23
0x34b655…2a6f
8 touches
6 conflicts
0xb59b0c85…f36c
0x34b655…2a6f
8 touches
6 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
8 touches
6 conflicts
0x94f7e861…70e3
0x34b655…2a6f
6 touches
3 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