← previous blocknext block →recent activity
Analyzing
Block #87,754,924
24 transactions · 22 stateful · 2026-07-14 18:36:42 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,754,924 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w18w29w311w212w313w414w116w518w221w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc204ea3…f1a3
0x34b655…2a6f
8 touches
6 conflicts
0x08547d8c…14ff
0x34b655…2a6f
6 touches
3 conflicts
0xa45d24aa…1b77
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
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
6 conflicts on slot 0xdc204ea323…a5f1a3
Audit this contract →
← previous block·next block →recent activity