← previous blocknext block →recent activity
Analyzing
Block #87,711,599
24 transactions · 21 stateful · 2026-07-14 13:46:44 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,711,599 · 24 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
7w08w19w212w013w315w416w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x84d74093…7808
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
10 conflicts on slot 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity