← previous blocknext block →recent activity

Analyzing

Block #86,990,641

15 transactions · 14 stateful · 2026-07-11 05:25:05 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.73

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,990,641  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xee4fe1f7…3ead

0x34b655…2a6f

6 touches
3 conflicts

0x072c4867…c7a9

0x34b655…2a6f

4 touches
1 conflict

0x0e9950ac…a02c

0x34b655…2a6f

4 touches
1 conflict

0x16649a8b…40b0

0x34b655…2a6f

4 touches
1 conflict

0x16649a8b…40b1

0x34b655…2a6f

4 touches
1 conflict

0x194be77e…58ae

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 0x0733be30d6…38112f

← previous block·next block →recent activity