← previous blocknext block →recent activity

Analyzing

Block #86,240,146

20 transactions · 16 stateful · 2026-07-07 17:47:43 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,240,146  ·  20 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

0x08330b36…ae29

0x34b655…2a6f

8 touches
6 conflicts

0xbcdee322…f454

0xa6afd3…d132

6 touches
3 conflicts

0x88cbd993…f3c9

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x23ef1567…8f31

0x34b655…2a6f

4 touches
1 conflict

0x353a3a00…5e0a

0x34b655…2a6f

4 touches
1 conflict

0x40aafdd2…46da

0x34b655…2a6f

4 touches
1 conflict

0x50887223…db7f

0x34b655…2a6f

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 0x08330b3687…a7ae29

← previous block·next block →recent activity