← previous blocknext block →recent activity

Analyzing

Block #73,374,006

13 transactions · 9 stateful · 2026-05-09 03:12:55 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,374,006  ·  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

0xa7fe0d97…ae1c

0x2a68ba…90c5

6 touches
3 conflicts

0x27451865…8c3a

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x080a3df3…9c8a

0x065c9d…c394

2 touches
1 conflict

0xd11260e7…3609

0x065c9d…c394

2 touches
1 conflict

0xa2a308cb…dc54

0x065c9d…c394

2 touches
0 conflicts

0x92d610a6…9a40

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xa7fe0d9788…69ae1c

← previous block·next block →recent activity