← previous blocknext block →recent activity

Analyzing

Block #87,331,344

23 transactions · 22 stateful · 2026-07-12 19:23:01 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

0.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,331,344  ·  23 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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x4caf91f9…8ab5

0x34b655…2a6f

8 touches
6 conflicts

0xa7013be2…c0a8

0x34b655…2a6f

8 touches
6 conflicts

0x2b98be55…d0df

0x34b655…2a6f

6 touches
3 conflicts

0x347327ff…3863

0x34b655…2a6f

6 touches
3 conflicts

0x90e113f8…c8f9

0xc8689a…ee79

6 touches
3 conflicts

0xb138d087…4689

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 0xfaef08b108…f90696

← previous block·next block →recent activity