← previous blocknext block →recent activity

Analyzing

Block #86,247,105

21 transactions · 17 stateful · 2026-07-07 18:34:17 UTC

Parallelism

86/100

Blocked

41%

Avg conflicts / tx

0.48

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,247,105  ·  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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xfefb0189…f726

0x34b655…2a6f

4 touches
1 conflict

0xd7d9628b…3608

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe06bbb2e…9416

0x34b655…2a6f

4 touches
1 conflict

0xe06bbb2e…9417

0x34b655…2a6f

4 touches
1 conflict

0xe2307994…acad

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 0xc824469a90…af6425

← previous block·next block →recent activity