← previous blocknext block →recent activity

Analyzing

Block #85,853,087

23 transactions · 18 stateful · 2026-07-05 22:45:01 UTC

Parallelism

83/100

Blocked

28%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,853,087  ·  23 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

0x1ccfa324…0b93

0x0a917f…7777

4 touches
1 conflict

0x44ad89ba…cf83

0x0a917f…7777

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x1517ed9b…659c

0x34b655…2a6f

4 touches
1 conflict

0x217bd767…b79e

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x83ff6d5d…4b75

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: 0x0a917fcc…9d7777

1 conflict on slot 0x1ccfa32498…500b93

← previous block·next block →recent activity