← previous blocknext block →recent activity

Analyzing

Block #86,811,712

29 transactions · 25 stateful · 2026-07-10 09:28:56 UTC

Parallelism

66/100

Blocked

48%

Avg conflicts / tx

1.48

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #86,811,712  ·  29 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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8d888c90…5479

0x34b655…2a6f

8 touches
6 conflicts

0x04ee1496…7bb7

0x34b655…2a6f

8 touches
6 conflicts

0xfaf3835b…98c7

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xa6d52fb7…c165

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 0xfaef08b108…f90696

← previous block·next block →recent activity