← previous blocknext block →recent activity

Analyzing

Block #86,629,846

17 transactions · 17 stateful · 2026-07-09 13:13:04 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,629,846  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x6c68ddc9…d106

0xb1dbf0…c0d3

4 touches
1 conflict

0x7f430e47…4cbd

0xb1dbf0…c0d3

4 touches
1 conflict

0x8a35acfb…d1aa

0xb1dbf0…c0d3

4 touches
1 conflict

0x8a35acfb…d1ab

0xb1dbf0…c0d3

4 touches
1 conflict

0xa4e9800f…4ab0

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab1

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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: 0x681e908b…e1ae09

1 conflict on slot 0x0d622e34f9…000000

← previous block·next block →recent activity