Block #73,273,782

← previous blocknext block →recent activity

Analyzing

Block #73,273,782

16 transactions · 15 stateful · 2026-05-08 16:06:08 UTC

Parallelism

56/100

Blocked

40%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,273,782  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0x13ca8f7a…fc54

0x065c9d…c394

4 touches
1 conflict

0x40fb6d33…3fa6

0x065c9d…c394

3 touches
1 conflict

0x5c37e5b8…9dc3

0x065c9d…c394

3 touches
1 conflict

0x2513043a…ab27

0x065c9d…c394

3 touches
1 conflict

0xa4f15ac4…7de2

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity