← previous blocknext block →recent activity

Analyzing

Block #75,079,765

22 transactions · 16 stateful · 2026-05-17 01:00:39 UTC

Parallelism

77/100

Blocked

50%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,079,765  ·  22 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

0x1bbdf58c…cd7a

0xd32edf…ff58

9 touches
10 conflicts

0x631b4113…baa9

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x26a96f1d…523f

0x34b655…2a6f

4 touches
1 conflict

0x8fbde2b3…9b8f

0x34b655…2a6f

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 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: 0xd32edf66…9fff58

10 conflicts on slot 0x1bbdf58cf7…59cd7a

← previous block·next block →recent activity