← previous blocknext block →recent activity

Analyzing

Block #75,502,159

13 transactions · 12 stateful · 2026-05-19 00:07:19 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.54

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,502,159  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

6 touches
3 conflicts

0x11e54ba3…2ca8

0xd32edf…ff58

5 touches
3 conflicts

0x96f39b8e…f795

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: 0x1b68626d…2de19c

3 conflicts on slot 0xd9f18d9a4a…7f141d

← previous block·next block →recent activity