← previous blocknext block →recent activity

Analyzing

Block #87,283,946

22 transactions · 20 stateful · 2026-07-12 14:06:05 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,283,946  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…0006

0x0a2fbf…29b1

8 touches
6 conflicts

0x208283d8…79d1

0x0a2fbf…29b1

8 touches
6 conflicts

0x208283d8…79d2

0x0a2fbf…29b1

8 touches
6 conflicts

0x208283d8…79d5

0x0a2fbf…29b1

8 touches
6 conflicts

0x2b4fc505…4b51

0x0a2fbf…29b1

8 touches
6 conflicts

0x2b4fc505…4b52

0x0a2fbf…29b1

8 touches
6 conflicts

0x0dd44476…ef40

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0005

0x370e2e…63b4

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: 0x0a2fbf2d…f729b1

6 conflicts on slot 0x0000000000…000006

← previous block·next block →recent activity