← previous blocknext block →recent activity

Analyzing

Block #75,717,765

25 transactions · 22 stateful · 2026-05-20 00:09:04 UTC

Parallelism

68/100

Blocked

41%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,717,765  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xb7b446d2…2006

0x34b655…2a6f

10 touches
10 conflicts

0x85a88798…f85e

0x34b655…2a6f

8 touches
6 conflicts

0x8fbde2b3…9b8f

0x34b655…2a6f

6 touches
3 conflicts

0x97d5efed…1aa4

0x34b655…2a6f

6 touches
3 conflicts

0x9baa8a2a…b9c8

0x34b655…2a6f

6 touches
3 conflicts

0xac206e47…ef7d

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity