← previous blocknext block →recent activity

Analyzing

Block #87,732,374

24 transactions · 23 stateful · 2026-07-14 16:05:52 UTC

Parallelism

88/100

Blocked

26%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,732,374  ·  24 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xc57b566d…8591

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x42f5c83a…a2d6

0x34b655…2a6f

4 touches
1 conflict

0x48ef64dc…7129

0x34b655…2a6f

4 touches
1 conflict

0x4b880990…8569

0x34b655…2a6f

4 touches
1 conflict

0x58266ec9…8ef7

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity