← previous blocknext block →recent activity

Analyzing

Block #86,954,267

19 transactions · 18 stateful · 2026-07-11 01:22:01 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,954,267  ·  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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x6d99ac64…0aa3

0x34b655…2a6f

6 touches
3 conflicts

0xfadc118d…5d64

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x97d5efed…1aa4

0x34b655…2a6f

4 touches
1 conflict

0xa6c4c171…5da8

0x34b655…2a6f

4 touches
1 conflict

0xa7013be2…c0a8

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

← previous block·next block →recent activity