← previous blocknext block →recent activity

Analyzing

Block #87,711,631

28 transactions · 22 stateful · 2026-07-14 13:46:56 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,711,631  ·  28 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xbf78ee7f…e7fd

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x3e8b3a49…53ee

0x34b655…2a6f

6 touches
3 conflicts

0x64929e6e…cf16

0x34b655…2a6f

6 touches
3 conflicts

0xac33ff75…077b

0xfa32f9…f3f0

4 touches
1 conflict

0x013a6b08…d120

0x34b655…2a6f

4 touches
1 conflict

0x0dd44476…ef40

0x34b655…2a6f

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

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 0xbf78ee7fb5…b5e7fd

← previous block·next block →recent activity