← previous blocknext block →recent activity

Analyzing

Block #87,731,802

18 transactions · 16 stateful · 2026-07-14 16:02:02 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,731,802  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

6 touches
3 conflicts

0x94ba9c4a…41d8

0x34b655…2a6f

6 touches
3 conflicts

0xc4de6652…13f4

0x34b655…2a6f

6 touches
3 conflicts

0x1da7723c…80ac

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

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

6 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity