← previous blocknext block →recent activity

Analyzing

Block #87,077,887

29 transactions · 21 stateful · 2026-07-11 15:07:47 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,077,887  ·  29 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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x0c9eb6ea…7c39

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x43ffd8bd…0d0c

0x34b655…2a6f

4 touches
1 conflict

0x44c93bf8…0a6b

0x34b655…2a6f

4 touches
1 conflict

0x5d863b2f…bd28

0x34b655…2a6f

4 touches
1 conflict

0x5f434145…4127

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity