← previous blocknext block →recent activity
Analyzing
Block #87,489,780
14 transactions · 12 stateful · 2026-07-13 13:02:30 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
1.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,489,780 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w08w39w110w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f5b72a…22e0
0x34b655…2a6f
10 touches
10 conflicts
0x521f03f8…dc0e
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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 0x22f5b72adb…1822e0
Audit this contract →
← previous block·next block →recent activity