← previous blocknext block →recent activity

Analyzing

Block #86,978,311

22 transactions · 17 stateful · 2026-07-11 04:02:39 UTC

Parallelism

77/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,978,311  ·  22 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

8 touches
6 conflicts

0x1941b441…5889

0x34b655…2a6f

8 touches
6 conflicts

0x05e76e1b…39ec

0x34b655…2a6f

6 touches
3 conflicts

0x17c3727d…cb0e

0x34b655…2a6f

4 touches
1 conflict

0x2356194c…0d6b

0x34b655…2a6f

4 touches
1 conflict

0x396ec98c…69d3

0x34b655…2a6f

4 touches
1 conflict

0x59f58019…2973

0x34b655…2a6f

4 touches
1 conflict

0x775a8ad3…8307

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 0xfaef08b108…f90696

← previous block·next block →recent activity