← previous blocknext block →recent activity

Analyzing

Block #86,222,129

21 transactions · 21 stateful · 2026-07-07 15:47:25 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,222,129  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x7bcd1d23…a2a8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0223e2e8…9862

0x34b655…2a6f

6 touches
3 conflicts

0xe06bbb2e…9417

0x34b655…2a6f

4 touches
1 conflict

0x706cd348…171e

0x065c9d…c394

4 touches
1 conflict

0x77ed432f…fa04

0x065c9d…c394

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