← previous blocknext block →recent activity

Analyzing

Block #74,646,803

28 transactions · 20 stateful · 2026-05-15 00:49:18 UTC

Parallelism

86/100

Blocked

55%

Avg conflicts / tx

0.79

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,646,803  ·  28 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x5c8c6ab6…dc36

0x065c9d…c394

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

4 touches
1 conflict

0xc9a9747f…e622

0x34b655…2a6f

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

6 conflicts on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity