← previous blocknext block →recent activity

Analyzing

Block #86,514,180

17 transactions · 15 stateful · 2026-07-09 00:18:19 UTC

Parallelism

82/100

Blocked

40%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,514,180  ·  17 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

0xf63d1c19…4e18

0x34b655…2a6f

6 touches
3 conflicts

0x4ec9ff52…e6f7

0x34b655…2a6f

6 touches
3 conflicts

0x23a320fb…cbd7

0x34b655…2a6f

6 touches
3 conflicts

0xe6c4128f…b7c2

0x34b655…2a6f

6 touches
3 conflicts

0x5ccbdfb6…3e06

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5317

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5318

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

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 0xf63d1c1918…294e18

← previous block·next block →recent activity