← previous blocknext block →recent activity

Analyzing

Block #73,210,926

11 transactions · 10 stateful · 2026-05-08 09:08:02 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,210,926  ·  11 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

0x64979bde…ba46

0x065c9d…c394

5 touches
3 conflicts

0x05c3f670…b61f

0x065c9d…c394

5 touches
3 conflicts

0x61337b97…e0ff

0x065c9d…c394

4 touches
1 conflict

0x67e78011…b5c2

0x065c9d…c394

4 touches
1 conflict

0x8864011d…db89

0x065c9d…c394

4 touches
1 conflict

0x8c2da147…c8c0

0x065c9d…c394

4 touches
1 conflict

0xa6f4fae7…411c

0x065c9d…c394

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity