← previous blocknext block →recent activity
Analyzing
Block #87,753,856
26 transactions · 26 stateful · 2026-07-14 18:29:34 UTC
Parallelism
85/100
Blocked
35%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,753,856 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w07w09w010w111w212w314w116w222w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x21c9fd73…dae4
0x34b655…2a6f
4 touches
1 conflict
0x28c62bca…b746
0x34b655…2a6f
4 touches
1 conflict
0x2f461725…5ab2
0x34b655…2a6f
4 touches
1 conflict
0x324ec4d3…f156
0x34b655…2a6f
4 touches
1 conflict
0x388633a0…86cd
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity