← previous blocknext block →recent activity

Analyzing

Block #86,690,620

21 transactions · 16 stateful · 2026-07-09 20:00:12 UTC

Parallelism

86/100

Blocked

38%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,690,620  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa08f40b2…9a93

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x001b7d74…69e0

0x34b655…2a6f

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x0b277fb8…2d81

0x34b655…2a6f

4 touches
1 conflict

0x0b277fb8…2d82

0x34b655…2a6f

4 touches
1 conflict

0x1535d171…c68b

0x34b655…2a6f

4 touches
1 conflict

0x19caa5cc…17c7

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

3 conflicts on slot 0xa08f40b255…099a93

← previous block·next block →recent activity