← previous blocknext block →recent activity

Analyzing

Block #86,618,972

20 transactions · 19 stateful · 2026-07-09 12:00:29 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,618,972  ·  20 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

0x8a35acfb…d1a8

0xb1dbf0…c0d3

8 touches
6 conflicts

0x205d7157…ce22

0xd32edf…ff58

7 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a7

0xb1dbf0…c0d3

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x07b979bc…3564

0xb1dbf0…c0d3

4 touches
1 conflict

0x6286219a…0721

0xb1dbf0…c0d3

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