← previous blocknext block →recent activity

Analyzing

Block #73,924,903

25 transactions · 21 stateful · 2026-05-11 16:35:35 UTC

Parallelism

72/100

Blocked

43%

Avg conflicts / tx

1.04

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,924,903  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xee230b20…5a0f

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x1319ae2c…7f9a

0x34b655…2a6f

4 touches
1 conflict

0x2aef4269…ad47

0x34b655…2a6f

4 touches
1 conflict

0x4f483049…3cc7

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity