← previous blocknext block →recent activity

Analyzing

Block #86,192,150

22 transactions · 18 stateful · 2026-07-07 12:27:12 UTC

Parallelism

77/100

Blocked

39%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,192,150  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xffa7d0a4…b10a

0x40c49f…2af0

8 touches
6 conflicts

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0x9991a26b…1b5d

0x40c49f…2af0

6 touches
3 conflicts

0xb005db54…e5ca

0x40c49f…2af0

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

4 touches
1 conflict

0xded5ec0c…f0fc

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity