← previous blocknext block →recent activity

Analyzing

Block #87,691,882

21 transactions · 19 stateful · 2026-07-14 11:34:36 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,691,882  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x8a5ced1c…3b29

0x34b655…2a6f

8 touches
6 conflicts

0xa5e7e081…b1fd

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x7dc98782…f193

0x34b655…2a6f

4 touches
1 conflict

0x836544ae…79e6

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 0xc824469a90…af6425

← previous block·next block →recent activity