← previous blocknext block →recent activity

Analyzing

Block #87,689,114

18 transactions · 16 stateful · 2026-07-14 11:16:07 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.89

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,689,114  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa86351b8…2c5a

0x34b655…2a6f

8 touches
6 conflicts

0x53f393fa…00b9

0x34b655…2a6f

8 touches
6 conflicts

0x182e11cf…8f19

0x34b655…2a6f

6 touches
3 conflicts

0x5b145de0…367c

0xc8689a…ee79

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x49f75237…44f4

0x34b655…2a6f

6 touches
3 conflicts

0x4f51d069…d0b4

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

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

6 conflicts on slot 0xa86351b861…d52c5a

← previous block·next block →recent activity