← previous blocknext block →recent activity

Analyzing

Block #86,628,768

19 transactions · 17 stateful · 2026-07-09 13:05:51 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

0.84

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,628,768  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x8a35acfb…d1a8

0xb1dbf0…c0d3

8 touches
6 conflicts

0x8a35acfb…d1a7

0xb1dbf0…c0d3

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x2700d3d0…f370

0x34b655…2a6f

6 touches
3 conflicts

0x7d6b9af1…9a38

0x34b655…2a6f

6 touches
3 conflicts

0xda46a376…f6a6

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xcc844ab5…4c6d

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: 0xb1dbf05f…b1c0d3

6 conflicts on slot 0x8a35acfbc1…6bd1a8

← previous block·next block →recent activity