← previous blocknext block →recent activity

Analyzing

Block #87,749,127

20 transactions · 16 stateful · 2026-07-14 17:57:56 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,749,127  ·  20 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

0x9a2de05d…3e6b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e7ebfe…1293

0x34b655…2a6f

4 touches
1 conflict

0x44231245…5442

0x34b655…2a6f

4 touches
1 conflict

0x4755fafb…859b

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x517d8281…14d1

0x34b655…2a6f

4 touches
1 conflict

0x517d8281…14d2

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 0x9a2de05d75…453e6b

← previous block·next block →recent activity