← previous blocknext block →recent activity

Analyzing

Block #87,616,355

28 transactions · 26 stateful · 2026-07-14 03:09:52 UTC

Parallelism

71/100

Blocked

54%

Avg conflicts / tx

1.64

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,616,355  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x25329a48…4e00

0x34b655…2a6f

16 touches
28 conflicts

0x2c53a187…3646

0x34b655…2a6f

16 touches
28 conflicts

0xe6fd65c0…3a8a

0x34b655…2a6f

14 touches
21 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x5170a218…3a84

0xc8689a…ee79

12 touches
15 conflicts

0x1175233a…64e7

0x34b655…2a6f

12 touches
15 conflicts

0x68b75835…d6f3

0x34b655…2a6f

12 touches
15 conflicts

0xa0af25f7…9129

0x34b655…2a6f

12 touches
15 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

28 conflicts on slot 0x25329a483e…ac4e00

← previous block·next block →recent activity