← previous blocknext block →recent activity

Analyzing

Block #87,612,300

24 transactions · 22 stateful · 2026-07-14 02:42:44 UTC

Parallelism

63/100

Blocked

55%

Avg conflicts / tx

1.96

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,612,300  ·  24 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

0xd2453506…54e4

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

12 touches
15 conflicts

0x326a02b5…8dad

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x4467ecee…e95b

0x34b655…2a6f

8 touches
6 conflicts

0x17cc5ec3…ae0e

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xa0af25f7…9129

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

15 conflicts on slot 0xd2453506e1…f954e4

← previous block·next block →recent activity