← previous blocknext block →recent activity

Analyzing

Block #86,849,968

26 transactions · 24 stateful · 2026-07-10 13:44:48 UTC

Parallelism

62/100

Blocked

46%

Avg conflicts / tx

1.19

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #86,849,968  ·  26 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x510c8ab3…95d5

0x34b655…2a6f

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x505d32fe…14ad

0x34b655…2a6f

6 touches
3 conflicts

0x5fee1ba0…2520

0x34b655…2a6f

6 touches
3 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x7cb193fe…ffa2

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 0x510c8ab361…cb95d5

← previous block·next block →recent activity