← previous blocknext block →recent activity

Analyzing

Block #75,743,454

12 transactions · 12 stateful · 2026-05-20 03:00:05 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,743,454  ·  12 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

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xdfa159d0…1576

0x065c9d…c394

6 touches
3 conflicts

0x1fff6dcb…b3f4

0xc8689a…ee79

4 touches
1 conflict

0xa17ec269…7cdd

0x1d1325…2305

4 touches
1 conflict

0xa605468c…1bfc

0x1d1325…2305

4 touches
1 conflict

0xc8525006…2b45

0x1d1325…2305

4 touches
1 conflict

0x0aa885fa…a3d1

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity