← previous blocknext block →recent activity

Analyzing

Block #87,410,765

21 transactions · 18 stateful · 2026-07-13 04:14:13 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,410,765  ·  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

0x2b5101ac…090b

0x34b655…2a6f

6 touches
3 conflicts

0x095a2c84…6648

0x34b655…2a6f

6 touches
3 conflicts

0x925dfa51…2cba

0x34b655…2a6f

6 touches
3 conflicts

0x21ea036d…5d37

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

6 touches
3 conflicts

0x80ce19e2…37d3

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

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 0x2b5101acd1…7c090b

← previous block·next block →recent activity