← previous blocknext block →recent activity

Analyzing

Block #86,674,487

22 transactions · 20 stateful · 2026-07-09 18:12:31 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,674,487  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf726e2e2…e561

0x34b655…2a6f

6 touches
3 conflicts

0xf5042875…9a93

0x34b655…2a6f

6 touches
3 conflicts

0x620b761c…270e

0x34b655…2a6f

6 touches
3 conflicts

0xdb3937e8…23cb

0x34b655…2a6f

6 touches
3 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

6 touches
3 conflicts

0x173337fe…f0af

0x34b655…2a6f

6 touches
3 conflicts

0x7ffd40fa…5112

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