← previous blocknext block →recent activity

Analyzing

Block #86,357,649

18 transactions · 17 stateful · 2026-07-08 06:52:23 UTC

Parallelism

72/100

Blocked

47%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,357,649  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…0002

0x04fdea…47d7

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x459573ed…fbbe

0x34b655…2a6f

4 touches
1 conflict

0x00e97699…c5a6

0x34b655…2a6f

2 touches
0 conflicts

0x209c6c7b…6b6d

0x34b655…2a6f

2 touches
0 conflicts

0x482471ad…122f

0x34b655…2a6f

2 touches
0 conflicts

0x4c04ce68…d007

0x34b655…2a6f

2 touches
0 conflicts

0x4d4389b2…6e07

0x34b655…2a6f

2 touches
0 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: 0x04fdeac2…f747d7

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity