← previous blocknext block →recent activity

Analyzing

Block #86,762,351

21 transactions · 19 stateful · 2026-07-10 03:59:19 UTC

Parallelism

86/100

Blocked

37%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,762,351  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x07d8b1e8…78c6

0x34b655…2a6f

6 touches
3 conflicts

0xb464ddb5…9036

0x065c9d…c394

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x0a0cecef…4ed0

0x34b655…2a6f

4 touches
1 conflict

0x0ae69c4a…0c0f

0x34b655…2a6f

4 touches
1 conflict

0x25e3730b…24a9

0x34b655…2a6f

4 touches
1 conflict

0x2dff59d9…f5e6

0x34b655…2a6f

4 touches
1 conflict

0x340d7cbb…84cf

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 0x07d8b1e8f0…0978c6

← previous block·next block →recent activity