← previous blocknext block →recent activity

Analyzing

Block #86,238,640

24 transactions · 18 stateful · 2026-07-07 17:37:40 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,238,640  ·  24 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

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x08330b36…ae29

0x34b655…2a6f

4 touches
1 conflict

0x1c796c6b…064e

0x34b655…2a6f

4 touches
1 conflict

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x396485b3…7e8f

0x34b655…2a6f

4 touches
1 conflict

0x49c1b7da…2c47

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5318

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity