← previous blocknext block →recent activity

Analyzing

Block #86,675,306

30 transactions · 23 stateful · 2026-07-09 18:18:00 UTC

Parallelism

77/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,675,306  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x0d488000…3831

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x275e37e9…a0b4

0x34b655…2a6f

4 touches
1 conflict

0x0682a731…d1e7

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 0x482471adbb…39122f

← previous block·next block →recent activity