← previous blocknext block →recent activity

Analyzing

Block #75,479,183

36 transactions · 21 stateful · 2026-05-18 21:29:38 UTC

Parallelism

75/100

Blocked

67%

Avg conflicts / tx

1.42

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,479,183  ·  36 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

0x17606ba6…1b6e

0x754704…b603

18 touches
36 conflicts

0x56a919c4…ab49

0xee8c0e…1242

8 touches
6 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

6 touches
3 conflicts

0x00000000…0000

0x094452…0a09

6 touches
3 conflicts

0x00000000…0003

0x094452…0a09

6 touches
3 conflicts

0x00000000…0004

0x094452…0a09

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x9e223b01…38b2

0x3bd359…433a

6 touches
3 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: 0x754704bc…afb603

36 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity