← previous blocknext block →recent activity

Analyzing

Block #87,640,074

23 transactions · 22 stateful · 2026-07-14 05:48:28 UTC

Parallelism

52/100

Blocked

59%

Avg conflicts / tx

2.39

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,640,074  ·  23 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

0x08330b36…ae29

0x34b655…2a6f

20 touches
45 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x5b145de0…367c

0xc8689a…ee79

12 touches
15 conflicts

0x21c9fd73…dae4

0x34b655…2a6f

12 touches
15 conflicts

0x312e4698…54c0

0x34b655…2a6f

12 touches
15 conflicts

0x49f75237…44f4

0x34b655…2a6f

12 touches
15 conflicts

0x4ca1448c…9de6

0x34b655…2a6f

12 touches
15 conflicts

0x9599eb41…b5d6

0x34b655…2a6f

12 touches
15 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

45 conflicts on slot 0x08330b3687…a7ae29

← previous block·next block →recent activity