← previous blocknext block →recent activity

Analyzing

Block #87,714,137

19 transactions · 16 stateful · 2026-07-14 14:03:44 UTC

Parallelism

74/100

Blocked

56%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,714,137  ·  19 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

0x88413c1a…7783

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xc0fb0790…a482

0x34b655…2a6f

6 touches
3 conflicts

0x2385516f…eca5

0x34b655…2a6f

4 touches
1 conflict

0x24d58d14…f7a5

0x34b655…2a6f

4 touches
1 conflict

0x4f1e16d4…4833

0x34b655…2a6f

4 touches
1 conflict

0x51134e2a…e079

0x34b655…2a6f

4 touches
1 conflict

0x5bf44783…6166

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 0x88413c1a8a…857783

← previous block·next block →recent activity