← previous blocknext block →recent activity

Analyzing

Block #86,238,418

28 transactions · 17 stateful · 2026-07-07 17:36:11 UTC

Parallelism

82/100

Blocked

41%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,238,418  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0xbcdee322…f454

0xa6afd3…d132

6 touches
3 conflicts

0x006ee1d9…5485

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xb7b446d2…2006

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x48028c31…6829

0x34b655…2a6f

4 touches
1 conflict

0x57330c5d…9973

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

3 conflicts on slot 0x08330b3687…a7ae29

← previous block·next block →recent activity