← previous blocknext block →recent activity

Analyzing

Block #86,136,689

25 transactions · 19 stateful · 2026-07-07 06:17:01 UTC

Parallelism

84/100

Blocked

37%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,136,689  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x8e80434a…a96d

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x332ecd85…ec0d

0x065c9d…c394

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a568

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity