← previous blocknext block →recent activity

Analyzing

Block #87,580,657

26 transactions · 19 stateful · 2026-07-13 23:11:07 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,580,657  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0xcc11c0f6…5670

0x34b655…2a6f

6 touches
3 conflicts

0x2d651956…12e8

0x34b655…2a6f

6 touches
3 conflicts

0x6be79ced…ccac

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x377b6d32…174e

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

6 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity