← previous blocknext block →recent activity

Analyzing

Block #87,716,260

17 transactions · 17 stateful · 2026-07-14 14:18:01 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

1.18

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,716,260  ·  17 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

0x8b818135…eff8

0x34b655…2a6f

10 touches
10 conflicts

0x2dfde2ed…8801

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x67905f6e…02a1

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xd8675136…9a01

0x34b655…2a6f

8 touches
6 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

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

10 conflicts on slot 0x8b81813549…3ceff8

← previous block·next block →recent activity