← previous blocknext block →recent activity

Analyzing

Block #86,959,437

20 transactions · 18 stateful · 2026-07-11 01:56:34 UTC

Parallelism

55/100

Blocked

61%

Avg conflicts / tx

1.85

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,959,437  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0x74888025…a5b8

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x92a5eb10…d5e3

0x34b655…2a6f

8 touches
6 conflicts

0xed660153…a905

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xc0b9bd73…7f1c

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity