← previous blocknext block →recent activity

Analyzing

Block #86,074,396

18 transactions · 17 stateful · 2026-07-06 23:21:19 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,074,396  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xef3f6769…4310

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x5d46e6a0…5ed9

0x40c49f…2af0

6 touches
3 conflicts

0x68ebc592…026d

0x40c49f…2af0

6 touches
3 conflicts

0x76d1e78d…7877

0x40c49f…2af0

6 touches
3 conflicts

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0xf9e23360…8ef7

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity