← previous blocknext block →recent activity

Analyzing

Block #87,716,107

25 transactions · 20 stateful · 2026-07-14 14:16:59 UTC

Parallelism

80/100

Blocked

30%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,716,107  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xdbadf6b0…43b2

0x33176b…e078

4 touches
1 conflict

0x5c591136…d322

0x34b655…2a6f

4 touches
1 conflict

0xc72cc4a8…bf3b

0xd32edf…ff58

3 touches
1 conflict

0xe14f51e5…e342

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e017

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity