← previous blocknext block →recent activity

Analyzing

Block #87,294,076

22 transactions · 19 stateful · 2026-07-12 15:13:50 UTC

Parallelism

50/100

Blocked

58%

Avg conflicts / tx

1.55

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,294,076  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x3ef0952c…762d

0x34b655…2a6f

8 touches
6 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x72880226…1435

0x34b655…2a6f

6 touches
3 conflicts

0x7b3da897…b268

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity