← previous blocknext block →recent activity

Analyzing

Block #86,250,284

23 transactions · 21 stateful · 2026-07-07 18:55:33 UTC

Parallelism

74/100

Blocked

38%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,250,284  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb56f0740…7542

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3b6e959d…158f

0x34b655…2a6f

4 touches
1 conflict

0x423af0c6…8145

0x34b655…2a6f

4 touches
1 conflict

0x5fbfe81c…a0a6

0x34b655…2a6f

4 touches
1 conflict

0x7d6b9af1…9a38

0x34b655…2a6f

4 touches
1 conflict

0x8e5cc690…b06b

0x34b655…2a6f

4 touches
1 conflict

0x99c093c1…9cd0

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 0xb56f0740e2…c17542

← previous block·next block →recent activity