← previous blocknext block →recent activity
Analyzing
Block #87,759,081
17 transactions · 16 stateful · 2026-07-14 19:04:29 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,759,081 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w29w011w112w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x28c62bca…b746
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x747f609d…1555
0x34b655…2a6f
6 touches
3 conflicts
0x8de38574…ad6e
0x34b655…2a6f
6 touches
3 conflicts
0x9ae859db…2d84
0x34b655…2a6f
6 touches
3 conflicts
0xaa643d44…2122
0x34b655…2a6f
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 0x9001f5497d…54089d
Audit this contract →
← previous block·next block →recent activity