← previous blocknext block →recent activity

Analyzing

Block #86,315,196

24 transactions · 19 stateful · 2026-07-08 02:08:54 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,315,196  ·  24 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

0x00000000…0001

0xfa32f9…f3f0

6 touches
3 conflicts

0x99f666e3…b2a2

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0xfa32f9…f3f0

6 touches
3 conflicts

0x9194f4a3…10b8

0x754704…b603

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xe90b7bce…c2e0

0xfa32f9…f3f0

6 touches
3 conflicts

0x59dbc306…f976

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: 0xfa32f9ec…fef3f0

3 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity