← previous blocknext block →recent activity

Analyzing

Block #74,247,539

11 transactions · 8 stateful · 2026-05-13 04:24:28 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,247,539  ·  11 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

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x84da660a…5a39

0x065c9d…c394

3 touches
1 conflict

0x8485a5d5…6907

0x065c9d…c394

2 touches
0 conflicts

0xb11add75…06d2

0x065c9d…c394

2 touches
0 conflicts

0xb37e7401…d4e6

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity