← previous blocknext block →recent activity

Analyzing

Block #87,691,271

23 transactions · 22 stateful · 2026-07-14 11:30:31 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

1.22

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,691,271  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x1616f80b…6c6e

0x34b655…2a6f

12 touches
15 conflicts

0x182e11cf…8f19

0x34b655…2a6f

12 touches
15 conflicts

0x5b145de0…367c

0xc8689a…ee79

12 touches
15 conflicts

0x49f75237…44f4

0x34b655…2a6f

12 touches
15 conflicts

0xed59b1cd…8509

0x34b655…2a6f

12 touches
15 conflicts

0x4f51d069…d0b4

0x34b655…2a6f

12 touches
15 conflicts

0x6fe7d366…78ff

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

21 conflicts on slot 0xa86351b861…d52c5a

← previous block·next block →recent activity