← previous blocknext block →recent activity

Analyzing

Block #87,325,756

19 transactions · 17 stateful · 2026-07-12 18:45:39 UTC

Parallelism

68/100

Blocked

41%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,325,756  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xdc8d4ee0…def3

0x34b655…2a6f

8 touches
6 conflicts

0x71641e8d…a781

0x34b655…2a6f

8 touches
6 conflicts

0x2a7c9c41…65ec

0x34b655…2a6f

8 touches
6 conflicts

0xa9f59232…f58c

0x34b655…2a6f

6 touches
3 conflicts

0x727fbce7…0c80

0x34b655…2a6f

6 touches
3 conflicts

0x4c214bb3…c5d3

0x34b655…2a6f

6 touches
3 conflicts

0x1ebe108b…72a0

0x34b655…2a6f

6 touches
3 conflicts

0x99618bc1…5db4

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 0xdc8d4ee099…56def3

← previous block·next block →recent activity