← previous blocknext block →recent activity

Analyzing

Block #86,977,979

27 transactions · 22 stateful · 2026-07-11 04:00:26 UTC

Parallelism

52/100

Blocked

59%

Avg conflicts / tx

1.96

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #86,977,979  ·  27 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x7e5ea60a…c4aa

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x0733be30…112f

0x34b655…2a6f

12 touches
15 conflicts

0x1941b441…5889

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x02c4bb0f…f2c8

0x34b655…2a6f

6 touches
3 conflicts

0x21683d77…4e07

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

21 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity