← previous blocknext block →recent activity

Analyzing

Block #87,133,072

19 transactions · 17 stateful · 2026-07-11 21:16:30 UTC

Parallelism

84/100

Blocked

29%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,133,072  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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…c4ab

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x27545031…a830

0x34b655…2a6f

4 touches
1 conflict

0x2e9fbe3c…aaf9

0x34b655…2a6f

4 touches
1 conflict

0x3133f94b…f76b

0x34b655…2a6f

4 touches
1 conflict

0x5e02109f…c11b

0x34b655…2a6f

4 touches
1 conflict

0x64e5f38d…187c

0x34b655…2a6f

4 touches
1 conflict

0x6b2ba712…0214

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 0x7e5ea60ab2…b0c4ab

← previous block·next block →recent activity