← previous blocknext block →recent activity

Analyzing

Block #73,923,973

20 transactions · 18 stateful · 2026-05-11 16:29:23 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

2.05

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,923,973  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x40cf4abc…da56

0x065c9d…c394

4 touches
1 conflict

0xf5319e84…8f86

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

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