← previous blocknext block →recent activity

Analyzing

Block #86,855,952

20 transactions · 17 stateful · 2026-07-10 14:24:50 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.85

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,855,952  ·  20 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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x469dac8d…3411

0x34b655…2a6f

4 touches
1 conflict

0x7b67f6cf…0aab

0x34b655…2a6f

4 touches
1 conflict

0xafb1c036…a5e4

0x34b655…2a6f

4 touches
1 conflict

0xc10b903d…2f54

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 0xfaef08b108…f90696

← previous block·next block →recent activity