← previous blocknext block →recent activity

Analyzing

Block #86,955,065

23 transactions · 16 stateful · 2026-07-11 01:27:21 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,955,065  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x78cb41e1…f2c1

0xfa32f9…f3f0

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x99f666e3…b2a2

0x3bd359…433a

6 touches
3 conflicts

0x9194f4a3…10b8

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0000

0xfa32f9…f3f0

6 touches
3 conflicts

0x00000000…0001

0xfa32f9…f3f0

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

3 conflicts on slot 0x78cb41e1aa…78f2c1

← previous block·next block →recent activity