← previous blocknext block →recent activity

Analyzing

Block #75,479,142

24 transactions · 17 stateful · 2026-05-18 21:29:22 UTC

Parallelism

75/100

Blocked

41%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,479,142  ·  24 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x846f2172…fd54

0x0555e3…2b9c

6 touches
3 conflicts

0x62e20208…be65

0x0555e3…2b9c

6 touches
3 conflicts

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0000

0x094452…0a09

6 touches
3 conflicts

0x00000000…0004

0x094452…0a09

6 touches
3 conflicts

0x9e223b01…38b2

0x3bd359…433a

6 touches
3 conflicts

0x070c4c81…4a42

0xd32edf…ff58

5 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: Kuru Exchange: Market-MON/USDC

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity