← previous blocknext block →recent activity

Analyzing

Block #87,588,919

23 transactions · 19 stateful · 2026-07-14 00:06:22 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,588,919  ·  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

0xd93edb3f…94ec

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x34d95d94…3a16

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x21c9fd73…dae4

0x34b655…2a6f

8 touches
6 conflicts

0x875164c2…f8a2

0x34b655…2a6f

8 touches
6 conflicts

0x9fd37234…2731

0x34b655…2a6f

8 touches
6 conflicts

0xa24365bc…5064

0x34b655…2a6f

8 touches
6 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 0xd93edb3f20…0394ec

← previous block·next block →recent activity