← previous blocknext block →recent activity

Analyzing

Block #75,846,252

20 transactions · 16 stateful · 2026-05-20 14:25:35 UTC

Parallelism

65/100

Blocked

38%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,846,252  ·  20 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x5d6da397…6c5c

0x34b655…2a6f

6 touches
3 conflicts

0x374426df…f445

0xc8689a…ee79

4 touches
1 conflict

0x20282983…15f3

0x34b655…2a6f

4 touches
1 conflict

0x4118bd12…924a

0x34b655…2a6f

4 touches
1 conflict

0x45de70d9…e1dc

0x34b655…2a6f

4 touches
1 conflict

0x80b0653d…5706

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity