← previous blocknext block →recent activity

Analyzing

Block #73,968,760

8 transactions · 8 stateful · 2026-05-11 21:27:17 UTC

Parallelism

50/100

Blocked

38%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,968,760  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x949bc521…2e49

0x065c9d…c394

4 touches
1 conflict

0xb78344e0…90d1

0x065c9d…c394

3 touches
1 conflict

0xcddc8b7c…f3e9

0x065c9d…c394

3 touches
1 conflict

0x184229dc…04fc

0x065c9d…c394

2 touches
0 conflicts

0x192b7774…ee47

0x065c9d…c394

2 touches
0 conflicts

0x634b6033…52d6

0x065c9d…c394

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity