← previous blocknext block →recent activity
Analyzing
Block #87,705,976
28 transactions · 26 stateful · 2026-07-14 13:09:06 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,705,976 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w27w38w49w510w616w217w118w226w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6389d47…9a28
0x34b655…2a6f
16 touches
28 conflicts
0x7837c02d…0965
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x67905f6e…02a1
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xeeaba9d3…b491
0x34b655…2a6f
14 touches
21 conflicts
0x4560e5a8…b741
0x34b655…2a6f
14 touches
21 conflicts
0x7a916b05…8a00
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xa6389d470d…f19a28
Audit this contract →
← previous block·next block →recent activity