← previous blocknext block →recent activity

Analyzing

Block #73,353,399

11 transactions · 9 stateful · 2026-05-09 00:55:56 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,353,399  ·  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

0x8876d94c…8435

0x2a68ba…90c5

6 touches
3 conflicts

0x46e3556e…c645

0xa6afd3…d132

5 touches
3 conflicts

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0xbdff944d…447e

0x2a68ba…90c5

4 touches
1 conflict

0x0adacc97…12a4

0x065c9d…c394

4 touches
1 conflict

0xf50cd4fa…0316

0xd32edf…ff58

3 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

2 touches
0 conflicts

0x00000000…0002

0xab3526…fa38

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 0x8876d94c2a…cc8435

← previous block·next block →recent activity