← previous blocknext block →recent activity

Analyzing

Block #73,961,086

13 transactions · 8 stateful · 2026-05-11 20:36:11 UTC

Parallelism

77/100

Blocked

25%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,961,086  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x5c155442…a55d

0x065c9d…c394

2 touches
0 conflicts

0x60c412fc…c292

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0000

0x139aab…382b

2 touches
0 conflicts

0x00000000…0001

0x139aab…382b

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity