← previous blocknext block →recent activity

Analyzing

Block #86,217,365

23 transactions · 22 stateful · 2026-07-07 15:15:39 UTC

Parallelism

70/100

Blocked

32%

Avg conflicts / tx

0.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,217,365  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xacd1b162…bee6

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2b71397c…741f

0x34b655…2a6f

4 touches
1 conflict

0x32409e80…a396

0x34b655…2a6f

4 touches
1 conflict

0x4c619b7d…f4fa

0x34b655…2a6f

4 touches
1 conflict

0x5c00b008…f838

0x34b655…2a6f

4 touches
1 conflict

0x7e17e82a…9748

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