← previous blocknext block →recent activity

Analyzing

Block #86,957,855

19 transactions · 17 stateful · 2026-07-11 01:46:00 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,957,855  ·  19 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

0x94de4d05…ad01

0x34b655…2a6f

6 touches
3 conflicts

0x0d9c5df5…66d4

0x34b655…2a6f

4 touches
1 conflict

0x13938a09…5f88

0x34b655…2a6f

4 touches
1 conflict

0x216ffe66…1f94

0x34b655…2a6f

4 touches
1 conflict

0x23ef1567…8f31

0x34b655…2a6f

4 touches
1 conflict

0x258fcaf5…2084

0x34b655…2a6f

4 touches
1 conflict

0x4688dd30…ef52

0x34b655…2a6f

4 touches
1 conflict

0x68c07cb9…ae14

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 0x94de4d05c1…d4ad01

← previous block·next block →recent activity