← previous blocknext block →recent activity

Analyzing

Block #86,756,810

24 transactions · 21 stateful · 2026-07-10 03:22:23 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,756,810  ·  24 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

0x00000000…003d

0x851145…3f07

8 touches
6 conflicts

0x8d0d8061…d410

0xc8689a…ee79

6 touches
3 conflicts

0x7a12283f…b18a

0x69df8a…6292

6 touches
3 conflicts

0x915c095e…c1e5

0x69df8a…6292

6 touches
3 conflicts

0xcfe06a18…b5b5

0x69df8a…6292

6 touches
3 conflicts

0xd8fd2add…50fc

0x69df8a…6292

6 touches
3 conflicts

0x81dbafca…d1ea

0x851145…3f07

6 touches
3 conflicts

0x8c42f949…c9d4

0x851145…3f07

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: 0x851145ea…9f3f07

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity