← previous blocknext block →recent activity

Analyzing

Block #86,628,305

23 transactions · 18 stateful · 2026-07-09 13:02:45 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,628,305  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

8 touches
6 conflicts

0x547f1bec…4423

0x34b655…2a6f

6 touches
3 conflicts

0x6b2ba712…0214

0x34b655…2a6f

6 touches
3 conflicts

0x727fbce7…0c80

0x34b655…2a6f

6 touches
3 conflicts

0x7523ad90…2ba5

0x34b655…2a6f

6 touches
3 conflicts

0x83afa561…34c2

0x34b655…2a6f

6 touches
3 conflicts

0x9df3af3f…fc46

0x34b655…2a6f

6 touches
3 conflicts

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 0xfaef08b108…f90696

← previous block·next block →recent activity