← previous blocknext block →recent activity

Analyzing

Block #73,501,479

13 transactions · 9 stateful · 2026-05-09 17:21:14 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,501,479  ·  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

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x8cdf3b42…dd9c

0x065c9d…c394

2 touches
0 conflicts

0xb2034294…06ab

0x065c9d…c394

2 touches
0 conflicts

0xbaec1ebe…9902

0x065c9d…c394

2 touches
0 conflicts

0xda6c31ec…ab5b

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity