← previous blocknext block →recent activity

Analyzing

Block #87,738,078

27 transactions · 26 stateful · 2026-07-14 16:44:01 UTC

Parallelism

70/100

Blocked

58%

Avg conflicts / tx

1.44

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,738,078  ·  27 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

0x9001f549…089d

0x34b655…2a6f

14 touches
21 conflicts

0x5b145de0…367c

0xc8689a…ee79

12 touches
15 conflicts

0x8d4c0bb9…ccd3

0x34b655…2a6f

12 touches
15 conflicts

0x22e7ebfe…1293

0x34b655…2a6f

12 touches
15 conflicts

0x3c0c2f32…c3df

0x34b655…2a6f

12 touches
15 conflicts

0x58620f29…db5a

0x34b655…2a6f

12 touches
15 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x37ee30c9…9e70

0x34b655…2a6f

10 touches
10 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

21 conflicts on slot 0x9001f5497d…54089d

← previous block·next block →recent activity