← previous blocknext block →recent activity
Analyzing
Block #87,713,011
35 transactions · 32 stateful · 2026-07-14 13:56:10 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
1.34
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,713,011 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w010w111w212w313w414w515w616w318w422w226w332w734w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x1526b11f…8b21
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x7be3246e…f89f
0x34b655…2a6f
8 touches
6 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0xa6389d47…9a28
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity