← previous blocknext block →recent activity

Analyzing

Block #87,671,300

22 transactions · 19 stateful · 2026-07-14 09:17:03 UTC

Parallelism

91/100

Blocked

26%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #87,671,300  ·  22 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

0x006c3b86…59a9

0x34b655…2a6f

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x08330b36…ae29

0x34b655…2a6f

4 touches
1 conflict

0x21c9fd73…dae4

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x2447fab0…811d

0x34b655…2a6f

4 touches
1 conflict

0x3c0c2f32…c3df

0x34b655…2a6f

4 touches
1 conflict

0x45606392…1234

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 0x006c3b8659…7a59a9

← previous block·next block →recent activity