← previous blocknext block →recent activity

Analyzing

Block #87,723,007

17 transactions · 16 stateful · 2026-07-14 15:03:11 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,723,007  ·  17 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

0x7ee6007b…fd68

0x34b655…2a6f

6 touches
3 conflicts

0x7fa1794c…3323

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x5f43f2bc…e94f

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x7c0bdc54…9dde

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

3 conflicts on slot 0x7ee6007b44…92fd68

← previous block·next block →recent activity