← previous blocknext block →recent activity

Analyzing

Block #86,702,424

27 transactions · 22 stateful · 2026-07-09 21:18:56 UTC

Parallelism

85/100

Blocked

36%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,702,424  ·  27 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x015c6c43…fa59

0x34b655…2a6f

4 touches
1 conflict

0x1b374c44…96d9

0x34b655…2a6f

4 touches
1 conflict

0x1d826725…e975

0x34b655…2a6f

4 touches
1 conflict

0x51a9fa57…1dff

0x34b655…2a6f

4 touches
1 conflict

0x56b5f5c0…a3ad

0x34b655…2a6f

4 touches
1 conflict

0x5a36d0c8…12e2

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity