← previous blocknext block →recent activity

Analyzing

Block #76,115,149

19 transactions · 16 stateful · 2026-05-21 20:17:20 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #76,115,149  ·  19 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0xaa47606d…91cb

0x9f3832…4ae4

4 touches
1 conflict

0x69cd5c19…88ca

0x9f3832…4ae4

4 touches
1 conflict

0x7cf5136f…ba69

0x9f3832…4ae4

4 touches
1 conflict

0xaa47606d…91ca

0x9f3832…4ae4

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

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