← previous blocknext block →recent activity

Analyzing

Block #86,755,376

19 transactions · 15 stateful · 2026-07-10 03:12:48 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,755,376  ·  19 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

6 touches
3 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

5 touches
3 conflicts

0xb07a0849…3b62

0xb1dbf0…c0d3

5 touches
3 conflicts

0x211d520a…bf67

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7d7ed9e4…4a59

0x34b655…2a6f

4 touches
1 conflict

0x7d7ed9e4…4a5a

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

← previous block·next block →recent activity