← previous blocknext block →recent activity

Analyzing

Block #74,750,711

17 transactions · 15 stateful · 2026-05-15 12:22:39 UTC

Parallelism

82/100

Blocked

20%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,750,711  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0280e591…5f98

0x065c9d…c394

2 touches
0 conflicts

0x24c3860b…ca49

0x065c9d…c394

2 touches
0 conflicts

0x6dc5e243…e5b6

0x065c9d…c394

2 touches
0 conflicts

0x77c6340d…4fc2

0x065c9d…c394

2 touches
0 conflicts

0xaa69eb0f…28a9

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 0xba38536db1…342b7d

← previous block·next block →recent activity