← previous blocknext block →recent activity

Analyzing

Block #87,724,137

21 transactions · 19 stateful · 2026-07-14 15:10:45 UTC

Parallelism

81/100

Blocked

32%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,724,137  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xcf5ef070…7d4f

0x34b655…2a6f

6 touches
3 conflicts

0xc40ea944…32b4

0x34b655…2a6f

6 touches
3 conflicts

0x4bc1abab…5874

0x34b655…2a6f

4 touches
1 conflict

0x5f917ce8…a3c3

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0xa38eb2fc…1658

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

6 conflicts on slot 0x0733be30d6…38112f

← previous block·next block →recent activity