← previous blocknext block →recent activity

Analyzing

Block #73,598,253

10 transactions · 9 stateful · 2026-05-10 04:04:19 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,598,253  ·  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

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x61f40d08…d885

0x065c9d…c394

4 touches
1 conflict

0xdca83b62…92f1

0x065c9d…c394

3 touches
1 conflict

0x32a9d34f…a94d

0x065c9d…c394

2 touches
0 conflicts

0x4ae4a77a…76e6

0x065c9d…c394

2 touches
0 conflicts

0x6060de18…3272

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

1 conflict on slot 0x4d87512b00…43897c

← previous block·next block →recent activity