← previous blocknext block →recent activity

Analyzing

Block #86,672,996

20 transactions · 18 stateful · 2026-07-09 18:02:34 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,672,996  ·  20 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

0xb6ed530c…d450

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x44429a9b…771d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4caf91f9…8ab5

0x34b655…2a6f

4 touches
1 conflict

0x5238dcb7…e0e2

0x34b655…2a6f

4 touches
1 conflict

0x57e03cb3…d7bb

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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

3 conflicts on slot 0xb6ed530c56…eed450

← previous block·next block →recent activity