← previous blocknext block →recent activity

Analyzing

Block #75,526,280

17 transactions · 14 stateful · 2026-05-19 02:52:23 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,526,280  ·  17 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

0xded5ec0c…f0fc

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x9210f658…c808

0x34b655…2a6f

6 touches
3 conflicts

0x5086c64a…28ba

0x34b655…2a6f

6 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

6 touches
3 conflicts

0x62c43c5f…f6b1

0xd32edf…ff58

5 touches
3 conflicts

0xd18a8dca…452a

0x1b6862…e19c

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 0xded5ec0c97…40f0fc

← previous block·next block →recent activity