← previous blocknext block →recent activity

Analyzing

Block #87,584,734

17 transactions · 14 stateful · 2026-07-13 23:38:24 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #87,584,734  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xfaf89f45…ced6

0x34b655…2a6f

4 touches
1 conflict

0xbaab6a38…dda5

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xe9452241…95a3

0x34b655…2a6f

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x1457c480…ae9f

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

1 conflict on slot 0xfaf89f4544…89ced6

← previous block·next block →recent activity