← previous blocknext block →recent activity

Analyzing

Block #86,664,912

21 transactions · 17 stateful · 2026-07-09 17:08:36 UTC

Parallelism

62/100

Blocked

59%

Avg conflicts / tx

1.19

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,664,912  ·  21 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

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0x1941b441…5889

0x34b655…2a6f

8 touches
6 conflicts

0xe5a9274d…78d7

0x34b655…2a6f

6 touches
3 conflicts

0x5f72d58f…c445

0x34b655…2a6f

6 touches
3 conflicts

0x814f0f40…c654

0x34b655…2a6f

6 touches
3 conflicts

0xd7d3e7dd…2bf3

0x34b655…2a6f

6 touches
3 conflicts

0x155dff63…2af8

0x34b655…2a6f

6 touches
3 conflicts

0xaba6578d…bd48

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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity