← previous blocknext block →recent activity

Analyzing

Block #73,043,149

25 transactions · 22 stateful · 2026-05-07 14:31:43 UTC

Parallelism

68/100

Blocked

41%

Avg conflicts / tx

0.96

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,043,149  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xce7bfe5e…5e58

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x251861eb…78fd

0x34b655…2a6f

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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

15 conflicts on slot 0xce7bfe5ef1…205e58

← previous block·next block →recent activity