← previous blocknext block →recent activity

Analyzing

Block #73,748,853

19 transactions · 14 stateful · 2026-05-10 20:58:10 UTC

Parallelism

74/100

Blocked

43%

Avg conflicts / tx

0.42

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,748,853  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf1aa1b6b…a435

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x762b786d…926e

0x065c9d…c394

4 touches
1 conflict

0x067c4363…b722

0x065c9d…c394

3 touches
1 conflict

0xbeccb5c0…9ebe

0x065c9d…c394

3 touches
1 conflict

0xd7b162cf…15a7

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity