← previous blocknext block →recent activity
Analyzing
Block #87,717,547
20 transactions · 18 stateful · 2026-07-14 14:26:41 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.85
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,717,547 · 20 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
2w03w14w06w07w18w210w111w112w313w215w318w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d85c11e…9c54
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xfa551be3…a911
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0x8f5cebcc…e9ea
0x065c9d…c394
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
3 conflicts on slot 0x6d85c11e6e…409c54
Audit this contract →
← previous block·next block →recent activity