← previous blocknext block →recent activity

Analyzing

Block #86,851,072

21 transactions · 18 stateful · 2026-07-10 13:52:10 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,851,072  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x818b0b44…ff6f

0x34b655…2a6f

4 touches
1 conflict

0x76d1e78d…7877

0x40c49f…2af0

4 touches
1 conflict

0xc66b77f3…d11a

0x40c49f…2af0

4 touches
1 conflict

0x94ba9c4a…41d8

0x34b655…2a6f

4 touches
1 conflict

0xc02ac297…5111

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