← previous blocknext block →recent activity

Analyzing

Block #73,324,152

10 transactions · 10 stateful · 2026-05-08 21:41:21 UTC

Parallelism

80/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,324,152  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x8d0dfe2c…3345

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xf79a5f45…bbcd

0x065c9d…c394

3 touches
1 conflict

0x44496494…b76c

0x065c9d…c394

3 touches
1 conflict

0x1d29a271…7467

0xd32edf…ff58

3 touches
1 conflict

0x8c913118…1aa1

0x065c9d…c394

2 touches
0 conflicts

0x936a9d1c…1ede

0x065c9d…c394

2 touches
0 conflicts

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity