← previous blocknext block →recent activity

Analyzing

Block #86,289,361

22 transactions · 20 stateful · 2026-07-07 23:16:16 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,289,361  ·  22 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

0xc7178f14…9efb

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0x79e8f935…c3b6

0x34b655…2a6f

6 touches
3 conflicts

0x0672e4a2…8d1f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0x04fdea…47d7

6 touches
3 conflicts

0xde93e7e6…f347

0x34b655…2a6f

4 touches
1 conflict

0x40970e69…da50

0x69df8a…6292

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 0xc7178f143f…479efb

← previous block·next block →recent activity