← previous blocknext block →recent activity

Analyzing

Block #87,749,520

20 transactions · 16 stateful · 2026-07-14 18:00:34 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x55c2c22c…0474

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x5586a02d…a1f2

0x34b655…2a6f

4 touches
1 conflict

0x6f46250b…3bf2

0x34b655…2a6f

4 touches
1 conflict

0xa249ae0e…1805

0x34b655…2a6f

4 touches
1 conflict

0xc36fa358…24cb

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 0x0733be30d6…38112f

← previous block·next block →recent activity