← previous blocknext block →recent activity

Analyzing

Block #86,793,955

22 transactions · 16 stateful · 2026-07-10 07:30:14 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,793,955  ·  22 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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x2e92f2eb…3869

0xd32edf…ff58

5 touches
3 conflicts

0x94ba9c4a…41d8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc6bb7e6c…bf35

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc8d31c56…91df

0x34b655…2a6f

4 touches
1 conflict

0x42041fec…bd86

0x754704…b603

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 0x92385428ad…dc6941

← previous block·next block →recent activity