← previous blocknext block →recent activity

Analyzing

Block #75,502,320

21 transactions · 17 stateful · 2026-05-19 00:08:23 UTC

Parallelism

57/100

Blocked

47%

Avg conflicts / tx

1.24

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,502,320  ·  21 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x8d1e5774…df46

0xd32edf…ff58

13 touches
21 conflicts

0x869ce236…bc53

0x065c9d…c394

7 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x10c19272…743f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

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

21 conflicts on slot 0x8d1e577482…e6df46

← previous block·next block →recent activity