← previous blocknext block →recent activity

Analyzing

Block #86,221,095

23 transactions · 19 stateful · 2026-07-07 15:40:31 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

0.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,221,095  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x7be3246e…f89f

0x34b655…2a6f

6 touches
3 conflicts

0x1526b11f…8b21

0x34b655…2a6f

6 touches
3 conflicts

0x882e3825…57d6

0x34b655…2a6f

6 touches
3 conflicts

0x89999c15…fdac

0x34b655…2a6f

4 touches
1 conflict

0x928d962f…f990

0x34b655…2a6f

4 touches
1 conflict

0x96dd83e6…a507

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: Perpl

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity