← previous blocknext block →recent activity

Analyzing

Block #86,803,161

35 transactions · 30 stateful · 2026-07-10 08:31:48 UTC

Parallelism

83/100

Blocked

23%

Avg conflicts / tx

0.26

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,803,161  ·  35 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xe2264392…d5f4

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x5a310d83…cae0

0x34b655…2a6f

4 touches
1 conflict

0x772ab420…c2f6

0x34b655…2a6f

4 touches
1 conflict

0xa6b89ebb…a66e

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity