← previous blocknext block →recent activity

Analyzing

Block #86,154,498

23 transactions · 19 stateful · 2026-07-07 08:15:54 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,154,498  ·  23 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

0x0a6f5e37…6c3c

0x34b655…2a6f

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x3a6290da…e683

0x34b655…2a6f

4 touches
1 conflict

0x3a7fb5b5…f0e5

0x34b655…2a6f

4 touches
1 conflict

0x4bfdcd51…9b58

0x34b655…2a6f

4 touches
1 conflict

0x4d3e58e0…a2d7

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