← previous blocknext block →recent activity
Analyzing
Block #87,578,366
33 transactions · 23 stateful · 2026-07-13 22:55:48 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,578,366 · 33 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
1w02w03w15w014w015w116w219w120w221w322w124w227w231w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x314add6a…c880
0x34b655…2a6f
8 touches
6 conflicts
0x830b63a6…8105
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x3f3d0666…5614
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x503b3a72…f6df
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 0x314add6a68…d5c880
Audit this contract →
← previous block·next block →recent activity