← previous blocknext block →recent activity

Analyzing

Block #87,504,070

46 transactions · 27 stateful · 2026-07-13 14:38:07 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.87

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,504,070  ·  46 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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0xcf827da3…f2a5

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

8 touches
6 conflicts

0xafb2524a…0ce4

0x34b655…2a6f

6 touches
3 conflicts

0x1836516b…7f6c

0x34b655…2a6f

6 touches
3 conflicts

0xb5c7c6aa…fdba

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity