← previous blocknext block →recent activity

Analyzing

Block #86,789,667

18 transactions · 18 stateful · 2026-07-10 07:01:38 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,789,667  ·  18 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

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0xec7fe04a…3c56

0x34b655…2a6f

6 touches
3 conflicts

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x0c15f714…46ab

0x34b655…2a6f

4 touches
1 conflict

0x2f28f5d5…fe07

0x34b655…2a6f

4 touches
1 conflict

0x44fc2746…0a53

0x34b655…2a6f

4 touches
1 conflict

0x4c2e78a1…2f95

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0xa6b89ebbaf…5fa66e

← previous block·next block →recent activity