← previous blocknext block →recent activity

Analyzing

Block #86,625,815

25 transactions · 21 stateful · 2026-07-09 12:46:07 UTC

Parallelism

64/100

Blocked

62%

Avg conflicts / tx

1.6

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,625,815  ·  25 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

0xfaef08b1…0696

0x34b655…2a6f

16 touches
28 conflicts

0x2bf5914f…c75d

0x34b655…2a6f

8 touches
6 conflicts

0x1cd9eb1d…f26f

0x34b655…2a6f

8 touches
6 conflicts

0xa020506f…7c60

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xfe8735de…fcd1

0x34b655…2a6f

8 touches
6 conflicts

0x660c9d95…7859

0x34b655…2a6f

6 touches
3 conflicts

0x78860c4f…cade

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

28 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity