← previous blocknext block →recent activity

Analyzing

Block #87,705,277

28 transactions · 25 stateful · 2026-07-14 13:04:25 UTC

Parallelism

82/100

Blocked

28%

Avg conflicts / tx

0.39

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,705,277  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x66cc379b…36fd

0x34b655…2a6f

6 touches
3 conflicts

0xee4fe1f7…3ead

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xed4604d7…11d2

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

6 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity