← previous blocknext block →recent activity
Analyzing
Block #87,579,034
24 transactions · 19 stateful · 2026-07-13 23:00:16 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,579,034 · 24 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
2w03w14w09w010w111w212w315w216w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x8d773511…5fd3
0x34b655…2a6f
6 touches
3 conflicts
0x503b3a72…f6df
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x77097867…4156
0x34b655…2a6f
4 touches
1 conflict
0x7799fd62…0d1c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
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