← previous blocknext block →recent activity

Analyzing

Block #87,716,875

27 transactions · 25 stateful · 2026-07-14 14:22:11 UTC

Parallelism

63/100

Blocked

44%

Avg conflicts / tx

1.04

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,716,875  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x7525206c…fbd5

0x34b655…2a6f

12 touches
15 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x4755fafb…859b

0x34b655…2a6f

8 touches
6 conflicts

0x67905f6e…02a1

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xbac273dd…36d5

0x34b655…2a6f

8 touches
6 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

8 touches
6 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 0x7525206cf5…dcfbd5

← previous block·next block →recent activity