← previous blocknext block →recent activity

Analyzing

Block #75,572,672

8 transactions · 6 stateful · 2026-05-19 08:00:55 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,572,672  ·  8 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

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x45ebd489…ec62

0x065c9d…c394

4 touches
1 conflict

0xe7424d33…bbd7

0x065c9d…c394

3 touches
1 conflict

0xa8720bc2…12d1

0x065c9d…c394

3 touches
1 conflict

0x6db7e52f…29e9

0x065c9d…c394

3 touches
1 conflict

0x9873c400…1ce7

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 0x443a3e479f…3af4a4

← previous block·next block →recent activity