← previous blocknext block →recent activity

Analyzing

Block #73,372,919

17 transactions · 16 stateful · 2026-05-09 03:05:42 UTC

Parallelism

65/100

Blocked

63%

Avg conflicts / tx

1.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,372,919  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0002

0xab3526…fa38

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x58e30630…5e65

0x065c9d…c394

4 touches
1 conflict

0x58cd10a0…817d

0x065c9d…c394

4 touches
1 conflict

0x38d51846…fd92

0x065c9d…c394

4 touches
1 conflict

0x62ad42e8…2e75

0x065c9d…c394

3 touches
1 conflict

0x1240b0b6…9158

0x065c9d…c394

3 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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity