← previous blocknext block →recent activity

Analyzing

Block #75,679,483

16 transactions · 11 stateful · 2026-05-19 19:54:33 UTC

Parallelism

81/100

Blocked

18%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,679,483  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

4 touches
1 conflict

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x4b42dd82…834a

0x065c9d…c394

2 touches
0 conflicts

0x6ca0d5ee…1571

0x065c9d…c394

2 touches
0 conflicts

0x7d4a64b7…ed92

0x065c9d…c394

2 touches
0 conflicts

0x8e04cd85…6caf

0x065c9d…c394

2 touches
0 conflicts

0xdc230eeb…d9bf

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity