← previous blocknext block →recent activity

Analyzing

Block #87,285,377

23 transactions · 19 stateful · 2026-07-12 14:15:38 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.91

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,285,377  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x8a35acfb…d1ac

0xb1dbf0…c0d3

8 touches
6 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

6 touches
3 conflicts

0x962b5b93…0ea2

0x34b655…2a6f

6 touches
3 conflicts

0x727fbce7…0c80

0x34b655…2a6f

4 touches
1 conflict

0x8fee8c28…7765

0x34b655…2a6f

4 touches
1 conflict

0xb2a25bac…c741

0x34b655…2a6f

4 touches
1 conflict

0xb39cb1d8…effa

0x34b655…2a6f

4 touches
1 conflict

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