← previous blocknext block →recent activity

Analyzing

Block #85,986,683

21 transactions · 17 stateful · 2026-07-06 13:35:35 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.43

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,986,683  ·  21 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

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x7fffd49d…772a

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xafd867b7…2b2e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd90a674b…29f7

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0xb364a9fe…6c2f

0x065c9d…c394

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

1 conflict on slot 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity