← previous blocknext block →recent activity

Analyzing

Block #73,393,438

27 transactions · 18 stateful · 2026-05-09 05:22:12 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.59

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,393,438  ·  27 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

0x4d87512b…897c

0x065c9d…c394

10 touches
10 conflicts

0xa7fe0d97…ae1c

0x2a68ba…90c5

8 touches
6 conflicts

0xafb9269d…3766

0x065c9d…c394

6 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xe038916c…b1be

0x2a68ba…90c5

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x7c403af1…31b1

0x3bd359…433a

4 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: 0x065c9d28…a9c394

10 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity