← previous blocknext block →recent activity

Analyzing

Block #86,703,531

26 transactions · 21 stateful · 2026-07-09 21:26:19 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,703,531  ·  26 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a8

0xb1dbf0…c0d3

4 touches
3 conflicts

0x8a35acfb…d1a9

0xb1dbf0…c0d3

4 touches
3 conflicts

0x898d9b8a…d1ef

0x34b655…2a6f

4 touches
1 conflict

0xbaf6ed88…c179

0x34b655…2a6f

4 touches
1 conflict

0xf346808d…6ad4

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity