← previous blocknext block →recent activity

Analyzing

Block #87,257,365

13 transactions · 12 stateful · 2026-07-12 11:08:22 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,257,365  ·  13 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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x01d29504…d21b

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x250bcb28…0a42

0x34b655…2a6f

4 touches
1 conflict

0x3483ab79…8ed3

0x34b655…2a6f

4 touches
1 conflict

0x388633a0…86cd

0x34b655…2a6f

4 touches
1 conflict

0x3ae90d94…cfba

0x34b655…2a6f

4 touches
1 conflict

0x52163873…f09f

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

← previous block·next block →recent activity