← previous blocknext block →recent activity

Analyzing

Block #85,791,827

34 transactions · 30 stateful · 2026-07-05 15:56:49 UTC

Parallelism

91/100

Blocked

17%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,791,827  ·  34 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

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x747f609d…1555

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0x87ee379a…cd9e

0x34b655…2a6f

3 touches
1 conflict

0x7a814f0d…35fd

0x3c2269…cf62

2 touches
0 conflicts

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