← previous blocknext block →recent activity

Analyzing

Block #74,483,096

11 transactions · 9 stateful · 2026-05-14 06:31:42 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.36

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,483,096  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x05bc9737…65e0

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x49eefc08…a65a

0x065c9d…c394

3 touches
1 conflict

0x6cb31628…c7e5

0x065c9d…c394

3 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

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

1 conflict on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity