← previous blocknext block →recent activity

Analyzing

Block #87,730,335

27 transactions · 25 stateful · 2026-07-14 15:52:13 UTC

Parallelism

74/100

Blocked

52%

Avg conflicts / tx

1.41

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,730,335  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

10 touches
10 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

10 touches
10 conflicts

0xd7e54f60…8bd3

0x34b655…2a6f

8 touches
6 conflicts

0xcf17589f…048c

0x34b655…2a6f

8 touches
6 conflicts

0x96bca57d…4d43

0x34b655…2a6f

6 touches
3 conflicts

0x767799cd…f423

0xc8689a…ee79

6 touches
3 conflicts

0x52f7c71c…d0a6

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity