← previous blocknext block →recent activity

Analyzing

Block #75,551,074

31 transactions · 20 stateful · 2026-05-19 05:37:11 UTC

Parallelism

71/100

Blocked

45%

Avg conflicts / tx

0.77

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,551,074  ·  31 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

0x84192918…8e2e

0xd32edf…ff58

11 touches
15 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

10 touches
10 conflicts

0xd84811f9…ab6e

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c0

0x1b6862…e19c

6 touches
3 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

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

15 conflicts on slot 0x8419291877…928e2e

← previous block·next block →recent activity