← previous blocknext block →recent activity

Analyzing

Block #87,749,869

23 transactions · 22 stateful · 2026-07-14 18:02:54 UTC

Parallelism

61/100

Blocked

41%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,749,869  ·  23 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

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0xc36fa358…24cb

0x34b655…2a6f

8 touches
6 conflicts

0x5067865d…de75

0x34b655…2a6f

6 touches
3 conflicts

0x367b69ad…33d8

0x34b655…2a6f

6 touches
3 conflicts

0x367b69ad…33d9

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 0xf3d10975b0…050d07

← previous block·next block →recent activity